Cyber Trackr - Free Compliance Library
Cyber Trackr
The Free Compliance Library

Microsoft Lync 2013 Security Technical Implementation Guide

  • Version/Release: V1R5
  • Published: 2024-06-14
  • Expand All:
  • Severity:
  • Sort:
Compare

Select any two versions of this STIG to compare the individual requirements

View

Select any old version/release of this STIG to view the previous requirements

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
b
The ability of Lync to store user passwords must be disabled.
IA-5 - Medium - CCI-000196 - V-242503 - SV-242503r961026_rule
RMF Control
IA-5
Severity
Medium
CCI
CCI-000196
Version
DTOO420
Vuln IDs
  • V-242503
  • V-40776
Rule IDs
  • SV-242503r961026_rule
  • SV-52834
Lync 2013 provides a single, unified client for real-time communications, including voice and video calls, Lync Meetings, presence, instant messaging, and persistent chat. These features require the ability to log into the service with a username and password. The Lync client could potentially be configured to store user passwords locally which would allow it to be susceptible to compromise and to be used maliciously.
Checks: C-45778r713212_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Allow storage of user passwords" is set to "Disabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Policies\Microsoft\office\15.0\lync Criteria: If the value savepassword is REG_DWORD = 0, this is not a finding.

Fix: F-45735r713213_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Allow storage of user passwords" to "Disabled".

b
Session Initiation Protocol (SIP) security mode must be configured.
SC-23 - Medium - CCI-001184 - V-242504 - SV-242504r961110_rule
RMF Control
SC-23
Severity
Medium
CCI
CCI-001184
Version
DTOO421
Vuln IDs
  • V-242504
  • V-40777
Rule IDs
  • SV-242504r961110_rule
  • SV-52835
Lync 2013 provides a single, unified client for real-time communications, including voice and video calls, Lync Meetings, presence, instant messaging, and persistent chat, using the Session Initiation Protocol (SIP). SIP is widely used for controlling multimedia communication sessions, such as voice and video calls over Internet Protocol (IP) networks. By using TLS it would render a sniff/man in the middle attack very difficult to impossible to achieve within the time period in which a given conversation could be attacked. TLS authenticates all parties and encrypts all traffic. This does not prevent listening over the wire, but the attacker cannot read the traffic unless the encryption is broken.
Checks: C-45779r713215_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Configure SIP security mode" is set to "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Policies\Microsoft\office\15.0\lync Criteria: If the value enablesiphighsecuritymode is REG_DWORD = 1, this is not a finding.

Fix: F-45736r713216_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Configure SIP security mode" to "Enabled".

b
In the event a secure Session Initiation Protocol (SIP) connection fails, the connection must be restricted from resorting to the unencrypted HTTP.
SC-23 - Medium - CCI-001184 - V-242505 - SV-242505r961110_rule
RMF Control
SC-23
Severity
Medium
CCI
CCI-001184
Version
DTOO422
Vuln IDs
  • V-242505
  • V-40778
Rule IDs
  • SV-242505r961110_rule
  • SV-52836
Lync 2013 provides a single, unified client for real-time communications, including voice and video calls, Lync Meetings, presence, instant messaging, and persistent chat. The Lync client has a fall back option so that, in the event the Lync client cannot make a secure SIP connection to the Lync server, it will fall back to an unencrypted HTTP connection. In that event, all traffic will be unencrypted and in clear text. The configuration must be set to prevent HTTP being used for SIP connections in the event TLS or TCP fail.
Checks: C-45780r713218_chk

Verify the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Disable HTTP fallback for SIP connection" is set to "Enabled". Procedure: Use the Windows Registry Editor to navigate to the following key: HKLM\Software\Policies\Microsoft\office\15.0\lync Criteria: If the value disablehttpconnect is REG_DWORD = 1, this is not a finding.

Fix: F-45737r713219_fix

Set the policy value for Computer Configuration -> Administrative Templates -> Microsoft Lync 2013 -> Microsoft Lync Feature Policies "Disable HTTP fallback for SIP connection" to "Enabled".

c
The version of Lync running on the system must be a supported version.
SI-2 - High - CCI-002605 - V-265903 - SV-265903r999913_rule
RMF Control
SI-2
Severity
High
CCI
CCI-002605
Version
DTOO999-Lync13
Vuln IDs
  • V-265903
Rule IDs
  • SV-265903r999913_rule
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).
Checks: C-69822r999911_chk

Lync 2013 is no longer supported by the vendor. If the system is running Lync 2013, this is a finding.

Fix: F-69726r999912_fix

Upgrade to a supported version.