StigData/Archive/Office/U_MS_Skype_for_Business_2016_STIG_V2R1_Manual-xccdf.xml
|
<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type='text/xsl' href='STIG_unclass.xsl'?><Benchmark xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cpe="http://cpe.mitre.org/language/2.0" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xsi:schemaLocation="http://checklists.nist.gov/xccdf/1.1 http://nvd.nist.gov/schema/xccdf-1.1.4.xsd http://cpe.mitre.org/dictionary/2.0 http://cpe.mitre.org/files/cpe-dictionary_2.1.xsd" id="Microsoft_Skype_for_Business_2016" xml:lang="en" xmlns="http://checklists.nist.gov/xccdf/1.1"><status date="2025-11-25">deprecated</status><title>Microsoft Skype for Business 2016 Security Technical Implementation Guide</title><description>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.</description><notice id="terms-of-use" xml:lang="en"></notice><front-matter xml:lang="en"></front-matter><rear-matter xml:lang="en"></rear-matter><reference href="https://cyber.mil"><dc:publisher>DISA</dc:publisher><dc:source>STIG.DOD.MIL</dc:source></reference><plain-text id="release-info">Release: 1 Benchmark Date: 05 Jan 2026</plain-text><plain-text id="generator">3.5.2</plain-text><plain-text id="conventionsVersion">1.10.0</plain-text><version>2</version><Profile id="MAC-1_Classified"><title>I - Mission Critical Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-1_Public"><title>I - Mission Critical Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-1_Sensitive"><title>I - Mission Critical Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-2_Classified"><title>II - Mission Support Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-2_Public"><title>II - Mission Support Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-2_Sensitive"><title>II - Mission Support Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-3_Classified"><title>III - Administrative Classified</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-3_Public"><title>III - Administrative Public</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Profile id="MAC-3_Sensitive"><title>III - Administrative Sensitive</title><description><ProfileDescription></ProfileDescription></description><select idref="V-238105" selected="true" /><select idref="V-238106" selected="true" /><select idref="V-238107" selected="true" /><select idref="V-279949" selected="true" /></Profile><Group id="V-238105"><title>SRG-APP-000516</title><description><GroupDescription></GroupDescription></description><Rule id="SV-238105r961863_rule" weight="10.0" severity="medium"><version>DTOO420</version><title>The ability to store user passwords in Skype must be disabled.
</title><description><VulnDiscussion>Allows Microsoft Lync to store user passwords. If you enable this policy setting, Microsoft Lync can store a password on request from the user. If you disable this policy setting, Microsoft Lync cannot store a password. If you do not configure this policy setting and the user logs on to a domain, Microsoft Lync does not store the password. If you do not configure this policy setting and the user does not log on to a domain (for example, if the user logs on to a workgroup), Microsoft Lync can store the password. Note: You can configure this policy setting under both Computer Configuration and User Configuration, but the policy setting under Computer Configuration takes precedence. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls></description><reference><dc:title>DPMS Target Microsoft Skype for Business 2016</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Microsoft Skype for Business 2016</dc:subject><dc:identifier>5314</dc:identifier></reference><ident system="http://cyber.mil/legacy">SV-85525</ident><ident system="http://cyber.mil/legacy">V-70901</ident><ident system="http://cyber.mil/cci">CCI-000366</ident><fixtext fixref="F-41274r651437_fix">Set the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> Microsoft Lync Feature Policies "Allow storage of user passwords" to "Disabled". </fixtext><fix id="F-41274r651437_fix" /><check system="C-41315r651436_chk"><check-content-ref href="Microsoft_Skype_for_Business_2016_STIG.xml" name="M" /><check-content>Verify the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> 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\16.0\lync Criteria: If the value savepassword is REG_DWORD = 0, this is not a finding.</check-content></check></Rule></Group><Group id="V-238106"><title>SRG-APP-000219</title><description><GroupDescription></GroupDescription></description><Rule id="SV-238106r1043178_rule" weight="10.0" severity="medium"><version>DTOO421</version><title>Session Initiation Protocol (SIP) security mode must be configured. </title><description><VulnDiscussion>When Lync connects to the server, it supports various authentication mechanisms. This policy allows the user to specify whether Digest and Basic authentication are supported. Disabled (default): NTLM/Kerberos/TLS-DSK/Digest/Basic Enabled: Authentication mechanisms: NTLM/Kerberos/TLS-DSK Gal Download: Requires HTTPS if user is not logged in as an internal user. </VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls></description><reference><dc:title>DPMS Target Microsoft Skype for Business 2016</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Microsoft Skype for Business 2016</dc:subject><dc:identifier>5314</dc:identifier></reference><ident system="http://cyber.mil/legacy">SV-85527</ident><ident system="http://cyber.mil/legacy">V-70903</ident><ident system="http://cyber.mil/cci">CCI-001184</ident><fixtext fixref="F-41275r651440_fix">Set the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> Microsoft Lync Feature Policies "Configure SIP security mode" to "Enabled". </fixtext><fix id="F-41275r651440_fix" /><check system="C-41316r651439_chk"><check-content-ref href="Microsoft_Skype_for_Business_2016_STIG.xml" name="M" /><check-content>Verify the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> 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\16.0\lync Criteria: If the value enablesiphighsecuritymode is REG_DWORD = 1, this is not a finding.</check-content></check></Rule></Group><Group id="V-238107"><title>SRG-APP-000219</title><description><GroupDescription></GroupDescription></description><Rule id="SV-238107r1043178_rule" weight="10.0" severity="medium"><version>DTOO422</version><title>In the event a secure Session Initiation Protocol (SIP) connection fails, the connection must be restricted from resorting to the unencrypted HTTP. </title><description><VulnDiscussion>Prevents from HTTP being used for SIP connection in case TLS or TCP fail.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls></description><reference><dc:title>DPMS Target Microsoft Skype for Business 2016</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Microsoft Skype for Business 2016</dc:subject><dc:identifier>5314</dc:identifier></reference><ident system="http://cyber.mil/legacy">SV-85529</ident><ident system="http://cyber.mil/legacy">V-70905</ident><ident system="http://cyber.mil/cci">CCI-001184</ident><fixtext fixref="F-41276r651443_fix">Set the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> Microsoft Lync Feature Policies "Disable HTTP fallback for SIP connection" to "Enabled". </fixtext><fix id="F-41276r651443_fix" /><check system="C-41317r651442_chk"><check-content-ref href="Microsoft_Skype_for_Business_2016_STIG.xml" name="M" /><check-content>Verify the policy value for Computer Configuration -> Administrative Templates -> Skype for Business 2016 -> 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\16.0\lync Criteria: If the value disablehttpconnect is REG_DWORD = 1, this is not a finding.</check-content></check></Rule></Group><Group id="V-279949"><title>SRG-APP-000456</title><description><GroupDescription></GroupDescription></description><Rule id="SV-279949r1156596_rule" weight="10.0" severity="high"><version>DTOSkype999</version><title>The version of Skype running on the system must be a supported version.</title><description><VulnDiscussion>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).</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls></description><reference><dc:title>DPMS Target Microsoft Skype for Business 2016</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Microsoft Skype for Business 2016</dc:subject><dc:identifier>5314</dc:identifier></reference><ident system="http://cyber.mil/cci">CCI-002605</ident><fixtext fixref="F-84415r1156595_fix">Upgrade to a supported version.</fixtext><fix id="F-84415r1156595_fix" /><check system="C-84510r1156594_chk"><check-content-ref href="Microsoft_Skype_for_Business_2016_STIG.xml" name="M" /><check-content>Skype is no longer supported by the vendor. If the system is running Skype, this is a finding.</check-content></check></Rule></Group></Benchmark> |