Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

Microsoft Lync 2013 STIG

V1R2 · · · Released 25 Apr 2014 · 3 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

The Microsoft Lync 2013 Security Technical Implementation Guide (STIG) is published as a tool to improve the security of Department of Defense (DoD) information systems. Comments or proposed revisions to this document should be sent via e-mail to the following address: disa.letterkenny.FSO.mbx.stig-customer-support-mailbox@mail.mil.
Sort by
b
The ability of Lync to store user passwords must be disabled.
MA-4 - Medium - CCI-001632 - V-40776 - SV-52834r1_rule
RMF Control
MA-4
Severity
M
CCI
CCI-001632
Version
DTOO420
Vuln IDs
  • V-40776
Rule IDs
  • SV-52834r1_rule
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.System AdministratorInformation Assurance Officer
Checks: C-47151r1_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-45760r1_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.
MA-4 - Medium - CCI-001632 - V-40777 - SV-52835r1_rule
RMF Control
MA-4
Severity
M
CCI
CCI-001632
Version
DTOO421
Vuln IDs
  • V-40777
Rule IDs
  • SV-52835r1_rule
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.System AdministratorInformation Assurance Officer
Checks: C-47152r1_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-45761r1_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.
MA-4 - Medium - CCI-001632 - V-40778 - SV-52836r2_rule
RMF Control
MA-4
Severity
M
CCI
CCI-001632
Version
DTOO422
Vuln IDs
  • V-40778
Rule IDs
  • SV-52836r2_rule
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.System AdministratorInformation Assurance Officer
Checks: C-47153r3_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-45762r2_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".