{
"id": 379,
"benchmarkId": "Microsoft_SharePoint_Server_2013",
"slug": "microsoft_sharepoint_2013",
"stigSlug": "microsoft_sharepoint_2013",
"versionStatus": "current",
"status": "accepted",
"statusDate": "2024-12-10T00:00:00.000Z",
"title": "Microsoft SharePoint 2013 Security Technical Implementation Guide",
"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.",
"version": "2",
"vendor": null,
"createdAt": "2025-10-21T11:31:03.876Z",
"updatedAt": "2025-10-23T20:54:33.768Z",
"groups": [
{
"id": 19411,
"benchmarkId": 379,
"groupId": "V-223270",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223270r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000175",
"ruleTitle": "The SharePoint setup account must be configured with the minimum privileges on the SQL server.",
"ruleVulnDiscussion": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action. \n\nThis requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts. \nThis policy limits the Farm Account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the \"Database Access\" account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint setup account with minimum privileges on the SQL server.\n\nConfigure the account on the SQL server.\n- Launch the SQL Server Management Console and navigate to Security >> Logins. \n- Select the SharePoint Setup User account.\n- Click on \"Server Roles\".\n- Ensure only public, dbcreator, and securityadmin roles are checked.\n- Remove checks from all other roles.",
"ruleFixId": "F-24931r430868_fix",
"ruleCheckSystem": "C-24943r430867_chk",
"ruleCheckContent": "The SharePoint setup account must be configured with the minimum privileges on the SQL server.\n\n- Launch the SQL Server Management Console and navigate to Security >> Logins. \n- Select the SharePoint Setup User account.\n- Click on \"Server Roles\" and verify only public, dbcreator, and securityadmin are checked.\n- Click on \"User Mapping\" and verify that the setup account is a member of the public and db_owner role on each SharePoint database.\n\nOtherwise, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19416,
"benchmarkId": 379,
"groupId": "V-223276",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223276r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000210",
"ruleTitle": "The SharePoint farm service account (database access account) must be configured with the minimum privileges for the local server.",
"ruleVulnDiscussion": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action. \n\nThis requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts. \nThis policy limits the Farm Account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the “Database Access” account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint farm service account (database access account) with the minimum privileges for the local server.\n\n- On the server(s) where the SharePoint software is installed, navigate to Server Manager >> Local Users and Groups.\n- Select the “Member of” tab. Configure the farm service account as a member of WSS_RESTRICTED_WPG, WSS_ADMIN_WPG, WSS_WPG, IIS_IUSRS, Performance Monitor User, Performance Log Users, and WSS groups. Remove all other group memberships from this account.\n- Select the other tabs in this area and remove other services or permissions configured for this account.",
"ruleFixId": "F-24937r802902_fix",
"ruleCheckSystem": "C-24949r802901_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the farm service account (database access account) is configured with the minimum privileges for the local server.\n\n- On the server(s) where the SharePoint software is installed, navigate to Server Manager >> Local Users and Groups.\n- Select the “Member of” tab and verify this account is only a member of the WSS_RESTRICTED_WPG, WSS_ADMIN_WPG, WSS_WPG, IIS_IUSRS, Performance Monitor User, Performance Log Users, and WSS groups.\n- Select the other tabs in this area to verify no other services or permissions are configured for this account.\n\nIf the farm service account is a member of any other groups than WSS_RESTRICTED_WPG, WSS_ADMIN_WPG, WSS_WPG, IIS_IUSRS, Performance Monitor User, Performance Log Users, and WSS groups on the local server where SharePoint is installed, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19381,
"benchmarkId": 379,
"groupId": "V-223238",
"title": "SRG-APP-000003",
"description": "",
"ruleId": "SV-223238r960741_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000005",
"ruleTitle": "SharePoint must support the requirement to initiate a session lock after 15 minutes of system or application inactivity has transpired.",
"ruleVulnDiscussion": "A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user to manually lock their application session prior to vacating the vicinity, applications need to be able to identify when a user's application session has idled and take action to initiate the session lock.\n\nThe session lock is implemented at the point where session activity can be determined and/or controlled. This is typically at the operating system level and results in a system lock, but it may be at the application level, where the application interface window is secured instead. The organization defines the period of inactivity that shall pass before a session lock is initiated, so this must be configurable.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000057",
"ruleFixText": "Configure the SharePoint server to lock the session lock after 15 minutes of inactivity.\n\nIn SharePoint Central Administration, click Application Management. \n\nOn the Application Management page, in the Web Applications section, click Manage web applications. \n\nPerform the following steps for each web application.\n- Select web application.\n- Select General Settings >> General Settings.\n- Navigate to Web Page Security Validation.\n- Set the \"Security validation is:\" property to On.\n- Set the \"Security validation expires:\" property to After.\n- Set the default time-out period to 15 minutes or less.\n- Select OK to save settings.",
"ruleFixId": "F-24899r430775_fix",
"ruleCheckSystem": "C-24911r430774_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure a session lock occurs after 15 minutes of inactivity.\n\nIn SharePoint Central Administration, click Application Management. \n\nOn the Application Management page, in the Web Applications section, click Manage web applications. \n\nVerify that each web application meets this requirement.\n- Select the web application.\n- Select General Settings >> General Settings.\n- Navigate to the Web Page Security Validation section.\n- Verify that the Security Validation is \"On\" and set to expire after 15 minutes or less. \n\nIf Security Validation is \"Off\" or if the default time-out period is not set to 15 minutes or less for any of the web applications, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19382,
"benchmarkId": 379,
"groupId": "V-223239",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223239r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000010",
"ruleTitle": "SharePoint must maintain and support the use of security attributes with stored information.",
"ruleVulnDiscussion": "Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information.\n\nThese attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information system and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy.\n\nOne example includes marking data as classified or FOUO. These security attributes may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security attributes are lost when the data is stored, there is the risk of a data compromise.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint server to maintain and support the use of security attributes with stored information.\n\nFrom the Site Collection Settings menu:\nAdd a column to Content Types that can hold \"security attributes\", e.g., FOUO, etc., and \"prompt the user to enter as metadata or properties to collect when documents of this content type are added to SharePoint.\"",
"ruleFixId": "F-24900r430778_fix",
"ruleCheckSystem": "C-24912r430777_chk",
"ruleCheckContent": "Review the SharePoint server to ensure the use of security attributes with stored information is maintained.\n\nClick Site Settings. \n\nUnder the Web Designer Galleries menu, click Site Content Types. \n\nDefine a set of Content Types that can hold \"security attributes\", e.g., FOUO, etc. \n\nFor each required Content Type, under \"Change Content Type Column\" ensure \"Required (Must contain information) is selected. Otherwise, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19383,
"benchmarkId": 379,
"groupId": "V-223240",
"title": "SRG-APP-000014",
"description": "",
"ruleId": "SV-223240r960759_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000015",
"ruleTitle": "SharePoint must utilize approved cryptography to protect the confidentiality of remote access sessions.",
"ruleVulnDiscussion": "Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless.\n\nRemote network access is accomplished by leveraging common communication protocols and establishing a remote connection. These connections will typically occur over either the public Internet or the Public Switched Telephone Network (PSTN). Since neither of these Internetworking mechanisms are private nor secure, if cryptography is not used, then the session data traversing the remote connection could be intercepted and compromised. Cryptography provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of confidentiality. The encryption strength of mechanism is selected based on the security categorization of the information traversing the remote connection.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000068",
"ruleFixText": "Configure the SharePoint server to use approved cryptography to protect the confidentiality of remote access sessions.\n\nOpen IIS Manager.\n\nIn the Connections pane, expand \"Sites\".\n\nClick the \"Web Application\" site.\n\nIn the Actions pane, click \"Bindings\".\n\nIn the Site Bindings window, click \"Add\".\n\nIn the Add Site Binding window, change \"Type\" to \"https\", and select the site's SSL certificate. Click \"OK\".\n\nRemove all bindings that do not use https.\n\nClick \"Close\".",
"ruleFixId": "F-24901r430781_fix",
"ruleCheckSystem": "C-24913r430780_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure approved cryptography is being utilized to protect the confidentiality of remote access sessions.\n\nNavigate to Central Administration.\n\nUnder “System Settings”, click “Configure Alternate Access mappings”.\n\nReview the “Public URL for zone” column values. If any URL does not begin with “https”, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19384,
"benchmarkId": 379,
"groupId": "V-223241",
"title": "SRG-APP-000015",
"description": "",
"ruleId": "SV-223241r960762_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000020",
"ruleTitle": "SharePoint must use cryptography to protect the integrity of the remote access session.",
"ruleVulnDiscussion": "Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless.\n\nRemote network access is accomplished by leveraging common communication protocols and establishing a remote connection. These connections will typically occur over the public Internet, the Public Switched Telephone Network (PSTN), or sometimes both. Since neither of these Internetworking mechanisms are private nor secure, if cryptography is not used, then the session data traversing the remote connection could be intercepted and potentially modified. Cryptography provides a means to secure the remote connection to prevent unauthorized access to the data traversing the remote access connection, thereby providing a degree of integrity. The encryption strength of a mechanism is selected based on the security categorization of the information traversing the remote connection.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001453",
"ruleFixText": "Configure the SharePoint server configuration to use cryptography to protect the integrity of the remote access session.\n\nOpen IIS Manager.\n\nIn the Connections pane, expand \"Sites\".\n\nClick the \"Web Application\" site.\n\nIn the Actions pane, click \"Bindings\".\n\nIn the Site Bindings window, click \"Add\".\n\nIn the Add Site Binding window, change \"Type\" to \"https\", and select the site's SSL certificate. Click \"OK\".\n\nRemove all bindings that do not use https.\n\nClick \"Close\".",
"ruleFixId": "F-24902r430784_fix",
"ruleCheckSystem": "C-24914r430783_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure cryptography is being used to protect the integrity of the remote access session.\n\nNavigate to Central Administration.\n\nUnder “System Settings”, click “Configure Alternate Access mappings”.\n\nReview the “Public URL for zone” column values. If any URL does not begin with “https”, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19385,
"benchmarkId": 379,
"groupId": "V-223242",
"title": "SRG-APP-000016",
"description": "",
"ruleId": "SV-223242r960765_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000025",
"ruleTitle": "SharePoint must ensure remote sessions for accessing security functions and security-relevant information are audited.",
"ruleVulnDiscussion": "Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless.\n\nRemote network and system access is accomplished by leveraging common communication protocols to establish a remote connection. These connections will typically originate over either the public Internet or the Public Switched Telephone Network (PSTN). Neither of these Internetworking mechanisms is private or secure, and they do not, by default, restrict access to networked resources once connectivity is established.\n\nNumerous best practices are employed to protect remote connections, such as utilizing encryption to protect data sessions and firewalls to restrict and control network connectivity. In addition to these protections, auditing must also be utilized in order to track system activity, assist in diagnosing system issues and provide evidence needed for forensic investigations post security incident.\n\nWhen organizations define security-related application functions or security-related application information, it is incumbent upon the application providing access to that data to ensure auditing of remote connectivity to those resources occurs in support of organizational requirements.\n\nRemote access to security functions (e.g., user management, audit log management, etc.) and security-relevant information requires the activity be audited by the organization. Any application providing remote access must support organizational requirements to audit access or organization-defined security functions and security-relevant information.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000067",
"ruleFixText": "Configure the SharePoint server configuration to audit remote sessions for accessing security functions and security-relevant information.\n\nIn Central Administration, click on Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nSelect \"Use the default RMS server specified in Active Directory\", or identify a specific server by selecting \"Use this RMS server:\" and entering the server name.\n\nConfigure information management policies in accordance with the system security plan requirements.",
"ruleFixId": "F-24903r430787_fix",
"ruleCheckSystem": "C-24915r430786_chk",
"ruleCheckContent": "Note: If no unsanctioned information is transferred, and has been documented by the Data Owner, IRM is not required. This requirement is Not Applicable.\n\nReview the SharePoint server configuration to ensure remote sessions for accessing security functions and security-relevant information are audited.\n\nVerify that SharePoint audit settings are configured at the site collection level in accordance with your system security plan.\n\nTo verify audit settings at the site collection level for each site collection level subject to auditing per the SSP:\n\nClick Settings >> Site settings.\n\nIf not at the root of your site collection, under Site Collection Administration, click Go to top level site settings. (Note: The Site Collection Administration section will not be available if you do not have the necessary permissions)\n\nOn the Site Settings page, under Site Collection Administration, click Site collection audit settings.\n\nOn the Configure Audit Settings page verify the events that are required to audit are selected, and then click OK. If nothing is selected, or the selected criteria do not match the SSP, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19386,
"benchmarkId": 379,
"groupId": "V-223243",
"title": "SRG-APP-000039",
"description": "",
"ruleId": "SV-223243r960804_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000030",
"ruleTitle": "SharePoint must enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy.",
"ruleVulnDiscussion": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information.\n\nFrom an application perspective, flow control is established once application data flow modeling has been completed. Data flow modeling can be described as the process of identifying, modeling, and documenting how data moves around an information system. Data flow modeling examines processes (activities that transform data from one form to another), data stores (the holding areas for data), external entities (what sends data into a system or receives data from a system), and data flows (routes by which data can flow).\n\nOnce the application data flows have been identified, corresponding flow controls can be applied at the appropriate points.\n\nA few examples of flow control restrictions include the following: keeping export-controlled information from being transmitted in the clear to the Internet and blocking information that is marked as classified but is being transported to an unapproved destination. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path.\n\nApplication-specific examples of flow control enforcement can be found in information protection software (e.g., guards, proxies, gateways, and cross domain solutions) employing rule sets or establishing configuration settings restricting information system services or providing message-filtering capability based on content (e.g., using key word searches or document characteristics).\n\nApplications providing information flow control must be able to enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy.\n\nSharePoint Central Administrator is a powerful management tool used to administer the farm. This server should be installed on a trusted network segment. This server should be used to run required services rather than user-oriented web applications.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001414",
"ruleFixText": "Configure the SharePoint server to enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy.\n\nRemove the application server from the DMZ.",
"ruleFixId": "F-24904r430790_fix",
"ruleCheckSystem": "C-24916r430789_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy are enforced.\n\nInspect the logical location of the server farm web front end servers on a network diagram.\n\nVerify the Central Administration site is not installed on a server located in a DMZ or other publicly accessible segment of the network.\n\nIf Central Administrator is installed on a publicly facing SharePoint server, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19387,
"benchmarkId": 379,
"groupId": "V-223244",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223244r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000035",
"ruleTitle": "SharePoint must identify data type, specification, and usage when transferring information between different security domains so policy restrictions may be applied.",
"ruleVulnDiscussion": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information.\n\nAn example of flow control restrictions includes the following: keeping export-controlled information from being transmitted in the clear to the Internet. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., users, networks, devices) within information systems and between interconnected systems.\n\nApplication-specific examples of flow control enforcement can be found in information protection software (e.g., guards, proxies, application layer gateways, and cross domain solutions) employing rule sets or establishing configuration settings restricting information system services or providing message-filtering capability based on content (e.g., using key word searches or document characteristics).\n\nFlow control is based on the characteristics of the information and/or the information path. Applications providing flow control must identify data type, specification, and usage when transferring information between different security domains so policy restrictions may be applied.\n\nA security domain is defined as a domain implementing a security policy and administered by a single authority.\n\nData type, specification, and usage includes using file naming to reflect the type of data being transferred and limiting data transfer based on file type.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint server to identify data type, specification, and usage when transferring information between different security domains so policy restrictions may be applied.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nSelect \"Use the default RMS server specified in Active Directory\" or identify a specific server by selecting \"Use this RMS server:\" and entering the server name.\n\nConfigure information management policies in accordance with the system security plan requirements.",
"ruleFixId": "F-24905r430793_fix",
"ruleCheckSystem": "C-24917r430792_chk",
"ruleCheckContent": "Note: If no data is exchanged between different security domains, and has been documented by the Data Owner, IRM is not required. This requirement is Not Applicable.\n\nReview the SharePoint server configuration to ensure data type, specification, and usage when transferring information between different security domains are identified so policy restrictions may be applied.\n\nAn IRM must be enabled in SharePoint. The Windows Rights Management Services (RMS) (or a comparable IRM product) can either be located through Active Directory or specified.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nIf \"Do not use IRM on this server\" is selected, or if a configuration error message is displayed (such as \"... IRM will not work until the client is configured properly\"), this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19417,
"benchmarkId": 379,
"groupId": "V-223277",
"title": "SRG-APP-000204",
"description": "",
"ruleId": "SV-223277r961080_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000105",
"ruleTitle": "SharePoint must validate the integrity of security attributes exchanged between systems.",
"ruleVulnDiscussion": "When data is exchanged between information systems, the security attributes associated with said data need to be maintained.\n\nSecurity attributes are an abstraction representing the basic properties or characteristics of an entity with respect to safeguarding information, typically associated with internal data structures (e.g., records, buffers, files) within the information system and used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy.\n\nSecurity attributes may be explicitly or implicitly associated with the information contained within the information system.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001158",
"ruleFixText": "Configure the SharePoint server to validate the integrity of security attributes exchanged between systems.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nSelect \"Use the default RMS server specified in Active Directory\", or identify a specific server by selecting \"Use this RMS server:\" and entering the server name.\n\nConfigure information management policies in accordance with the system security plan requirements.",
"ruleFixId": "F-24938r430889_fix",
"ruleCheckSystem": "C-24950r430888_chk",
"ruleCheckContent": "Note: If no data is exchanged between systems, and has been documented by the Data Owner, IRM is not required. This requirement is Not Applicable.\n\nReview the SharePoint server configuration to ensure the integrity of security attributes exchanged between systems is validated. \n\nAn IRM must be enabled in SharePoint. The Windows Rights Management Services (RMS) (or a comparable IRM product) can either be located through Active Directory or specified.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nIf \"Do not use IRM on this server\" is selected, or if a configuration error message is displayed (such as \"... IRM will not work until the client is configured properly\"), this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19388,
"benchmarkId": 379,
"groupId": "V-223245",
"title": "SRG-APP-000047",
"description": "",
"ruleId": "SV-223245r987620_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000040",
"ruleTitle": "SharePoint must provide the ability to prohibit the transfer of unsanctioned information in accordance with security policy.",
"ruleVulnDiscussion": "The application enforces approved authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy.\n\nInformation flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information.\n\nSpecific examples of flow control enforcement can be found in boundary protection devices (e.g., proxies, gateways, guards, encrypted tunnels, firewalls, and routers) employing rule sets or establishing configuration settings restricting information system services, providing a packet-filtering capability based on header information or message-filtering capability based on content (e.g., using key word searches or document characteristics).\n\nActions to support this requirement include, but are not limited to checking all transferred information for malware, implementing dirty word list searches on transferred information, and applying the same protection measures to metadata (e.g., security attributes) that is applied to the information payload.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001374",
"ruleFixText": "Configure the SharePoint server to prohibit the transfer of unsanctioned information in accordance with security policy.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nSelect \"Use the default RMS server specified in Active Directory\", or identify a specific server by selecting \"Use this RMS server:\" and entering the server name.\n\nConfigure information management policies in accordance with the system security plan requirements.",
"ruleFixId": "F-24906r430796_fix",
"ruleCheckSystem": "C-24918r430795_chk",
"ruleCheckContent": "Note: If no unsanctioned information is transferred, and has been documented by the Data Owner, IRM is not required. This requirement is Not Applicable.\n\nReview the SharePoint server configuration to ensure the transfer of unsanctioned information in accordance with security policy is prohibited.\n\nAn IRM must be enabled in SharePoint. The Windows Rights Management Services (RMS) (or a comparable IRM product) can either be located through Active Directory or specified.\n\nIn Central Administration, click Security.\n\nOn the Security page, in the Information policy list, click \"Configure information rights management\".\n\nIf \"Do not use IRM on this server\" is selected or if a configuration error message is displayed (such as \"... IRM will not work until the client is configured properly\"), this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19389,
"benchmarkId": 379,
"groupId": "V-223246",
"title": "SRG-APP-000068",
"description": "",
"ruleId": "SV-223246r960843_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000045",
"ruleTitle": "SharePoint must display an approved system use notification message or banner before granting access to the system.",
"ruleVulnDiscussion": "Applications are required to display an approved system use notification message or banner before granting access to the system providing privacy and security notices consistent with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance and stating that:\n\n(i) users are accessing a U.S. Government information system;\n(ii) system usage may be monitored, recorded, and subject to audit;\n(iii) unauthorized use of the system is prohibited and subject to criminal and civil penalties; and\n(iv) the use of the system indicates consent to monitoring and recording.\n\nSystem use notification messages can be implemented in the form of warning banners displayed when individuals log on to the information system.\n\nSystem use notification is intended only for information system access including an interactive logon interface with a human user and is not intended to require notification when an interactive interface does not exist.\n\nUse this banner for desktops, laptops, and other devices accommodating banners of 1300 characters. The banner shall be implemented as a click-through banner at logon (to the extent permitted by the operating system), meaning it prevents further activity on the information system unless and until the user executes a positive action to manifest agreement by clicking on a box indicating \"OK\".",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000048",
"ruleFixText": "Configure the SharePoint web application's home page to display the authorized DoD warning banner text on or before the logon page.",
"ruleFixId": "F-24907r430799_fix",
"ruleCheckSystem": "C-24919r430798_chk",
"ruleCheckContent": "Note: If no unsanctioned information is transferred, and has been documented by the Data Owner, IRM is not required. This requirement is Not Applicable.\n\nReview the SharePoint server configuration to ensure an approved system use notification message or banner is displayed before granting access to the system.\nBanner application occurs on a per-Web Application basis:\nObtain a listing of all SharePoint Web applications.\nOpen a Web browser and navigate to the SharePoint Web application home page.\nVerify the authorized DoD warning banner text is displayed on the SharePoint web application home page.\nIf the authorized DoD warning banner text is not displayed on the first screen of the SharePoint web application, this is a finding.\n\nNote: Supplementary Information: DoD Logon Banner\n\"You are accessing a U.S. Government (USG) Information System (IS) that is provided for USG-authorized use only.\nBy using this IS (which includes any device attached to this IS), you consent to the following conditions:\n-The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.\n-At any time, the USG may inspect and seize data stored on this IS.\n-Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.\n-This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.\n-Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement for details.\"",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19390,
"benchmarkId": 379,
"groupId": "V-223247",
"title": "SRG-APP-000090",
"description": "",
"ruleId": "SV-223247r960882_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000055",
"ruleTitle": "SharePoint must allow designated organizational personnel to select which auditable events are to be audited by specific components of the system.",
"ruleVulnDiscussion": "Audit records can be generated from various components within the information system, such as network interfaces, hard disks, modems, etc. From an application perspective, certain specific application functionalities may be audited as well.\n\nThe list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the list of all events for which the system is capable of generating audit records (i.e., auditable events, time stamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, filenames involved, and access control or flow control rules invoked).\n\nOrganizations may define the organizational personnel accountable for determining which application components shall provide auditable events.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000171",
"ruleFixText": "Configure the SharePoint server configuration to allow designated organizational personnel to select which auditable events are to be audited by specific components of the system.\n\nNavigate to Central Administration.\n\nClick \"Monitoring\".\n\nClick \"Configure Diagnostic Logging\".\n\nSelect the event categories and trace levels to match those defined by the organization's system security plan.\n\nRemember that a base set of events is always audited.\n\nClick \"Ok\".",
"ruleFixId": "F-24908r430802_fix",
"ruleCheckSystem": "C-24920r430801_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure designated organizational personnel are allowed to select which auditable events are to be audited by specific components of the system.\n\nNavigate to Central Administration.\n\nClick \"Monitoring\".\n\nClick \"Configure Diagnostic Logging\".\n\nValidate that the selected event categories and trace levels match those defined by the organization's system security plan.\n\nRemember that a base set of events are always audited.\n\nIf the selected event categories/trace levels are inconsistent with those defined in the organization's system security plan, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19391,
"benchmarkId": 379,
"groupId": "V-223248",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223248r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000060",
"ruleTitle": "SharePoint must reject or delay, as defined by the organization, network traffic generated above configurable traffic volume thresholds.",
"ruleVulnDiscussion": "It is critical when a system is at risk of failing to process audit logs as required; actions are automatically taken to mitigate the failure or risk of failure.\n\nOne method used to thwart the auditing system is for an attacker to attempt to overwhelm the auditing system with large amounts of irrelevant data. The end result is audit logs that are either overwritten and activity thereby erased or disk space that is exhausted and any future activity is no longer logged.\n\nIn many system configurations, the disk space allocated to the auditing system is separate from the disks allocated for the operating system; therefore, this may not result in a system outage.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure SharePoint to reject or delay, as defined by the organization or site SSP, network traffic generated above configurable traffic volume thresholds.\n\nLog on to the server.\n\nClick Start.\n\nType Internet Information Services Manager in the Search Bar, click Enter.\n\nDetermine which IIS Sites are subject to user traffic. This is generally the IIS site hosting the Content Web Application.\n\nFor each site IIS site subject to user traffic, select the site.\n\nClick Advanced Settings.\n\nExpand Connection Limits.\n\nEnsure the following settings possess a value:\n-Connection Time-Out\n-Maximum Bandwidth\n-Maximum Concurrent Connections\n\nRepeat steps for each site subject to user traffic.",
"ruleFixId": "F-24909r430805_fix",
"ruleCheckSystem": "C-24921r430804_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure network traffic generated above configurable traffic volume thresholds, as defined by the organization or site SSP, is rejected or delayed.\n\nLog on to the server.\n\nClick Start.\n\nType Internet Information Services Manager in the Search Bar, click Enter.\n\nDetermine which IIS Sites are subject to user traffic. This is generally the IIS site hosting the Content Web Application.\n\nFor each site IIS site subject to user traffic, select the site.\n\nClick Advanced Settings.\n\nExpand Connection Limits.\n\nEnsure the following settings possess a value:\n-Connection Time-Out\n-Maximum Bandwidth\n-Maximum Concurrent Connections\n\nRepeat steps for each site subject to user traffic.\n\nOtherwise, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19392,
"benchmarkId": 379,
"groupId": "V-223249",
"title": "SRG-APP-000112",
"description": "",
"ruleId": "SV-223249r960921_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000065",
"ruleTitle": "SharePoint must prevent the execution of prohibited mobile code.",
"ruleVulnDiscussion": "Decisions regarding the utilization of mobile code within organizational information systems need to include evaluations that help determine the potential for the code to cause damage to the system if used maliciously.\n\nMobile code technologies include, for example, Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations.\n\nApplications can prevent the execution of prohibited mobile code by leveraging architectures that provide a virtual execution environment sometimes referred to as a \"sandbox\". The mobile code is executed within this isolated environment apart from the host's indigenous operating environment that allows for mobile code capability restrictions and helps to prevent malicious code from accessing system resources and data.\n\nPolicy and procedures related to mobile code address preventing the introduction of unacceptable mobile code within the information system. The DoDI 8552.01 policy pertains to the use of mobile code technologies within DoD information systems.\n\nThe application must prevent the execution of prohibited mobile code.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001695",
"ruleFixText": "Configure SharePoint to prevent the execution of prohibited mobile code.\n\nNavigate to Central Administration.\n\nClick Manage Web Applications.\n\nFor each Web Application in the Farm:\n-Click on the Web Application to configure.\n-Click on the drop-down box below General Settings.\n-Click on General Settings in the drop down box.\n-Under Browser File Handling, verify that \"Strict\" is selected.\n\nIf \"Strict\" is not selected, this is a finding.\n\nMobile code can be further restricted to meet the policy of the organization:\n\nLog on to a farm server hosting Central Administration.\n\nClick Start and type SharePoint 2013 Management Shell followed by Enter.\n\nType $webApp = Get-SPWebApplication -Identity {URL} where {URL is the {URL} of the web application to configure.\n\nPress Enter.\n\nType $webApp.AllowedInlineDownloadedMimeTypes. Remove ({mime type}) where {mime type} represents the mime type to remove (e.g., application\\x-shockwave-flash).\n\nPress Enter.",
"ruleFixId": "F-24910r430808_fix",
"ruleCheckSystem": "C-24922r430807_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the execution of prohibited mobile code is prevented.\n\nNavigate to Central Administration.\n\nClick Manage Web Applications.\n\nFor each Web Application in the Farm:\n-Click on the Web Application to configure.\n-Click on the drop-down box below General Settings.\n-Click on General Settings in the drop down box.\n-Under Browser File Handling, verify that \"Strict\" is selected.\n\nIf \"Strict\" is not selected, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19393,
"benchmarkId": 379,
"groupId": "V-223250",
"title": "SRG-APP-000156",
"description": "",
"ruleId": "SV-223250r960993_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000075",
"ruleTitle": "SharePoint must use replay-resistant authentication mechanisms for network access to privileged accounts.",
"ruleVulnDiscussion": "An authentication process resists replay attacks if it is impractical to achieve a successful authentication by recording and replaying a previous authentication message.\n\nTechniques used to address this include protocols using nonces (e.g., numbers generated for a specific one-time use) or challenges (e.g., TLS, WS_Security), and time synchronous or challenge-response one-time authenticators.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001941",
"ruleFixText": "Configure the SharePoint server to use replay-resistant authentication mechanisms for network access to privileged accounts.\n\nIf the web application is using Integrated Windows Authentication as the claims provider, perform the following:\n\nOpen the Central Administration site, select \"Application Management\".\n\nOn the \"Application Management\" page, select \"Manage Web Applications\", select the web application that corresponds to the site reviewed in the \"Check\" section above, then click the \"Authentication Providers\" button in the ribbon.\n\nSelect the zone corresponding to the web application being reviewed, which will open the \"Edit Authentication\" dialog in the \"Claims Authentication Types\" section, select \"Negotiate (Kerberos)\" in the \"Integrated Windows Authentication\" dropdown, then click \"Save\".",
"ruleFixId": "F-24911r430811_fix",
"ruleCheckSystem": "C-24923r430810_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure replay-resistant authentication mechanisms for network access to privileged accounts are used.\n\nSharePoint must be configured to use Kerberos as the primary authentication provider.\n\nLog on to the server.\n\nClick Start.\n\nType Internet Information Services Manager in the Search Bar, click Enter.\n\nExpand the server node in the tree view and expand the \"Sites\" node.\n\n*For each...* Select a SharePoint Web Application site to review.\n\nIn the \"IIS\" section, double-click Authentication and then select \"Windows Authentication\".\n\nRight-click \"Windows Authentication\" and select \"Providers\".\n\nEnsure \"Negotiate\" is listed first. If NTLM is listed first in the Enabled Providers box, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19394,
"benchmarkId": 379,
"groupId": "V-223251",
"title": "SRG-APP-000180",
"description": "",
"ruleId": "SV-223251r961053_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000080",
"ruleTitle": "SharePoint must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).",
"ruleVulnDiscussion": "Non-organizational users include all information system users other than organizational users, which include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors, guest researchers, individuals from allied nations).\n\nNon-organizational users must be uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization when related to the use of anonymous access, such as accessing a web server.\n\nAccordingly, a risk assessment is used in determining the authentication needs of the organization.\n\nScalability, practicality, and security are simultaneously considered in balancing the need to ensure ease of use for access to federal information and information systems with the need to protect and adequately mitigate risk to organizational operations, organizational assets, individuals, other organizations, and the Nation.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000804",
"ruleFixText": "Configure SharePoint to uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).\n\nNavigate to Central Administration website.\n\nClick on \"Manage web applications\".\n\nClick the web application name.\n\nClick the \"Authentication Providers\" button in the \"Web Applications\" ribbon.\n\nClick each Zone, and clear the \"Enable anonymous access\" check box.\n\nClick \"Save\".\n\nRepeat steps for each web application.",
"ruleFixId": "F-24912r430814_fix",
"ruleCheckSystem": "C-24924r430813_chk",
"ruleCheckContent": "Review the SharePoint configuration to ensure non-organizational users (or processes acting on behalf of non-organizational users) are uniquely identified and authenticated.\n\nNavigate to Central Administration website.\n\nClick on \"Manage web applications\".\n\nClick the web application name.\n\nClick the \"Authentication Providers\" button in the \"Web Applications\" ribbon.\n\nClick each Zone, and verify that the \"Enable anonymous access\" check box is not selected.\n\nIf it is selected and the web application zone is not defined in the system security plan as allowing anonymous access, this is a finding.\n\nRepeat steps for each web application.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19395,
"benchmarkId": 379,
"groupId": "V-223252",
"title": "SRG-APP-000179",
"description": "",
"ruleId": "SV-223252r961050_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000085",
"ruleTitle": "SharePoint must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.",
"ruleVulnDiscussion": "Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for SharePoint. Different versions of the Windows Server OS and versions of SharePoint will have different suites available.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000803",
"ruleFixText": "Configure the SharePoint server to implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance.\n\nOpen MMC.\n\nClick “File”, “Add/Remove Snap-in”, and “add Group Policy Object Editor”.\n\nEnter a name for the Group Policy Object, or accept the default.\n\nClick “Finish”.\n\nClick “OK”.\n\nNavigate to Computer Policy >> Computer Configuration >> Administrative Templates >> Network >> SSL Configuration Settings.\n\nRight-click “SSL Configuration Settings”, click “SSL Cipher Suite Order”, and then click “Edit”.\n\nIn the “SSL Cipher Suite Order” dialog box, select \"Enabled\".\n\nUnder “Options”, in the “SSL Cipher Suites” text box, enter desired cipher suites that are not DES or RC4.\n\nClick “OK”.",
"ruleFixId": "F-24913r821358_fix",
"ruleCheckSystem": "C-24925r821357_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance are implemented.\n\nOpen Registry Editor.\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Cryptography\\Configuration\\SSL\\00010002\".\n\nIf the REG_SZ \"Functions\" value does not exist, this is a finding.\n\nOpen the REG_SZ \"Functions\" value.\n\nIf any DES or RC4 cipher suites exist in the text string, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19396,
"benchmarkId": 379,
"groupId": "V-223254",
"title": "SRG-APP-000514",
"description": "",
"ruleId": "SV-223254r961857_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000095",
"ruleTitle": "SharePoint must employ NSA-approved cryptography to protect classified information.",
"ruleVulnDiscussion": "Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for SharePoint. Different versions of the Windows Server OS and versions of SharePoint will have different suites available.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-002450",
"ruleFixText": "Configure SharePoint to employ NSA-approved cryptography to protect classified information.\n\nOpen MMC.\n\nClick “File”, “Add/Remove Snap-in”, and “add Group Policy Object Editor”.\n\nEnter a name for the Group Policy Object, or accept the default.\n\nClick “Finish”.\n\nClick “OK”.\n\nNavigate to Computer Policy >> Computer Configuration >> Administrative Templates >> Network >> SSL Configuration Settings.\n\nRight-click “SSL Configuration Settings”, click “SSL Cipher Suite Order”, and then click “Edit”.\n\nIn the “SSL Cipher Suite Order” dialog box, select \"Enabled\".\n\nUnder “Options”, in the “SSL Cipher Suites” text box, enter desired cipher suites that are not DES or RC4.\n\nClick “OK”.",
"ruleFixId": "F-24915r821361_fix",
"ruleCheckSystem": "C-24927r821360_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure NSA-approved cryptography is employed to protect classified information.\n\nOpen Registry Editor.\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Cryptography\\Configuration\\SSL\\00010002\".\n\nIf the REG_SZ \"Functions\" value does not exist, this is a finding.\n\nOpen the REG_SZ \"Functions\" value.\n\nIf any DES or RC4 cipher suites exist in the text string, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19397,
"benchmarkId": 379,
"groupId": "V-223255",
"title": "SRG-APP-000555",
"description": "",
"ruleId": "SV-223255r961866_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000100",
"ruleTitle": "SharePoint must employ FIPS-validated cryptography to protect unclassified information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals.",
"ruleVulnDiscussion": "Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for SharePoint. Different versions of the Windows Server OS and versions of SharePoint will have different suites available.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-002450",
"ruleFixText": "Configure SharePoint to employ FIPS-validated cryptography to protect unclassified information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals.\n\nOpen MMC.\n\nClick “File”, “Add/Remove Snap-in”, and “add Group Policy Object Editor”.\n\nEnter a name for the Group Policy Object, or accept the default.\n\nClick “Finish”.\n\nClick “OK”.\n\nNavigate to Computer Policy >> Computer Configuration >> Administrative Templates >> Network >> SSL Configuration Settings.\n\nRight-click “SSL Configuration Settings”, click “SSL Cipher Suite Order”, and then click “Edit”.\n\nIn the “SSL Cipher Suite Order” dialog box, select \"Enabled\".\n\nUnder “Options”, in the “SSL Cipher Suites” text box, enter desired cipher suites that are not DES or RC4.\n\nClick “OK”.",
"ruleFixId": "F-24916r821364_fix",
"ruleCheckSystem": "C-24928r821363_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure FIPS-validated cryptography is employed to protect unclassified information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals.\n\nOpen Registry Editor.\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Cryptography\\Configuration\\SSL\\00010002\".\n\nIf the REG_SZ \"Functions\" value does not exist, this is a finding.\n\nOpen the REG_SZ \"Functions\" value.\n\nIf any DES or RC4 cipher suites exist in the text string, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19398,
"benchmarkId": 379,
"groupId": "V-223257",
"title": "SRG-APP-000219",
"description": "",
"ruleId": "SV-223257r1043178_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000110",
"ruleTitle": "SharePoint must ensure authentication of both client and server during the entire session. An example of this is SSL Mutual Authentication.",
"ruleVulnDiscussion": "This control focuses on communications protection at the session, versus packet level.\n\nAt the application layer, session IDs are tokens generated by web applications to uniquely identify an application user's session. Web applications utilize session tokens or session IDs in order to establish application user identity. Proper use of session IDs addresses man-in-the-middle attacks, including session hijacking or insertion of false information into a session. This control is only implemented where deemed necessary by the organization (e.g., sessions in service-oriented architectures providing web-based services).",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001184",
"ruleFixText": "Configure the SharePoint server to ensure SSL Mutual authentication of both client and server during the entire session.\n\nOpen IIS Manager.\n\nIn the Connections pane, expand \"Sites\".\n\nClick the \"Web Application\" site.\n\nIn the Actions pane, click \"Bindings\".\n\nIn the Site Bindings window, click \"Add\".\n\nIn the Add Site Binding window, change \"Type\" to \"https\", and select the site's SSL certificate. Click \"OK\".\n\nRemove all bindings that do not use https.\n\nClick \"Close\".",
"ruleFixId": "F-24918r430829_fix",
"ruleCheckSystem": "C-24930r430828_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure SSL Mutual authentication of both client and server during the entire session.\n\nNavigate to Central Administration.\n\nUnder “System Settings”, click “Configure Alternate Access mappings”.\n\nReview the “Public URL for zone” column values. If any URL does not begin with “https”, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19399,
"benchmarkId": 379,
"groupId": "V-223258",
"title": "SRG-APP-000220",
"description": "",
"ruleId": "SV-223258r1043179_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000115",
"ruleTitle": "SharePoint must terminate user sessions upon user logoff, and when idle time limit is exceeded.",
"ruleVulnDiscussion": "This requirement focuses on communications protection at the application session, versus network packet level.\n\nSession IDs are tokens generated by web applications to uniquely identify an application user's session. Applications will make application decisions and execute business logic based on the session ID. Unique session identifiers or IDs are the opposite of sequentially generated session IDs that can be easily guessed by an attacker. Unique session IDs help to reduce predictability of said identifiers. Unique session IDs address man-in-the-middle attacks, including session hijacking or insertion of false information into a session. If the attacker is unable to identify or guess the session information related to pending application traffic, they will have more difficulty in hijacking the session or otherwise manipulating valid sessions. When a user logs off, or when any other session termination event occurs, the application must terminate the user session to minimize the potential for an attacker to hijack that particular user session.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001185",
"ruleFixText": "Configure the SharePoint server to terminate user sessions upon user logoff, and when idle time limit is exceeded.\n\nNavigate to Central Administration website.\n\nClick \"Application Management\".\n\nClick \"Manage Web Applications\".\n\nRepeat the following steps for each web application:\n-Select the web application.\n-Click \"General Settings\" in the \"Web Application\" ribbon.\n-In the \"Web Page Security Validation\" section, set \"Security Validation:\" to \"On\" and that the \"Security Validation Expires:\" setting is set to 15 minutes.",
"ruleFixId": "F-24919r430832_fix",
"ruleCheckSystem": "C-24931r430831_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure user sessions are terminated upon user logoff, and when idle time limit is exceeded.\n\nNavigate to Central Administration website.\n\nClick \"Application Management\".\n\nClick \"Manage Web Applications\".\n\nRepeat the following steps for each web application:\n-Select the web application.\n-Click \"General Settings\" in the \"Web Application\" ribbon.\n-In the \"Web Page Security Validation\" section, verify that \"Security Validation is:\" is set to \"On\" and that the \"Security Validation Expires:\" setting is set to 15 minutes.\n\nOtherwise, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19400,
"benchmarkId": 379,
"groupId": "V-223259",
"title": "SRG-APP-000441",
"description": "",
"ruleId": "SV-223259r961638_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000120",
"ruleTitle": "SharePoint must maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission. When transmitting data, applications need to leverage transmission protection mechanisms such as TLS, SSL VPNs, or IPSec.",
"ruleVulnDiscussion": "Preventing the disclosure of transmitted information requires that applications take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPSec tunnel.\n\nAlternative physical protection measures include protected distribution systems. Protective Distribution Systems (PDS) are used to transmit unencrypted classified NSI through an area of lesser classification or control. Inasmuch as the classified NSI is unencrypted, the PDS must provide adequate electrical, electromagnetic, and physical safeguards to deter exploitation. Refer to NSTSSI No. 7003 for additional details on a PDS.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-002420",
"ruleFixText": "Configure the SharePoint server to maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission.\n\nOpen IIS Manager.\n\nIn the Connections pane, expand Sites.\n\nClick the Web Application site.\n\nIn the Actions pane, click Bindings.\n\nIn the Site Bindings window, click Add.\n\nIn the Add Site Binding window, change Type to https, and select the site's SSL certificate.\n\nClick OK, and then click Close.",
"ruleFixId": "F-24920r430835_fix",
"ruleCheckSystem": "C-24932r430834_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission is maintained.\n\nIn SharePoint Central Administration, click Application Management.\n\nOn the Application Management page, in the Web Applications list, click Manage web applications.\n\nOn the Web Applications Management page, verify that each Web Application URL begins with https.\n\nIf the URL does not begin with https, this is a finding.\n\nIf SharePoint communications between all components and clients are protected by alternative physical measures that have been approved by the AO, this is not a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19401,
"benchmarkId": 379,
"groupId": "V-223260",
"title": "SRG-APP-000219",
"description": "",
"ruleId": "SV-223260r1043178_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000125",
"ruleTitle": "SharePoint must implement an information system isolation boundary that minimizes the number of nonsecurity functions included within the boundary containing security functions.",
"ruleVulnDiscussion": "The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains) controlling access to and protecting the integrity of, the hardware, software, and firmware that perform those security functions. The information system maintains a separate execution domain (e.g., address space) for each executing process.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001184",
"ruleFixText": "Configure the SharePoint server to implement an information system isolation boundary that minimizes the number of nonsecurity functions included within the boundary containing security functions.\n\nLog on to the server that hosts the farm's Central Administration website.\n\nOpen IIS Manager.\n\nExpand \"Sites\" tree view and right-click the web application named \"SharePoint Central Administration\".\n\nSelect \"Edit Bindings ...\".\n\nSelect the site binding record and click \"Edit\".\n\nFrom the \"IP Address\" dropdown list, select an OOB IP address.\n\nClick \"Ok\".\n\n*NOTE: If the Central Administration site has multiple site bindings, steps will need to be repeated for each site binding.",
"ruleFixId": "F-24921r430838_fix",
"ruleCheckSystem": "C-24933r430837_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure an information system isolation boundary that minimizes the number of nonsecurity functions included within the boundary containing security functions are implemented.\n\nLog on to the server that hosts the farm's Central Administration website.\n\nOpen IIS Manager.\n\nExpand \"Sites\" tree view and right-click the web application named \"SharePoint Central Administration\".\n\nSelect \"Edit Bindings ...\".\n\nConfirm the site is bound to an out-of-band (OOB) IP address.\n\nIf the site is bound to a production IP address or not bound to a specific IP address, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19402,
"benchmarkId": 379,
"groupId": "V-223261",
"title": "SRG-APP-000238",
"description": "",
"ruleId": "SV-223261r987636_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000130",
"ruleTitle": "SharePoint must implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.",
"ruleVulnDiscussion": "The information system isolates security functions from nonsecurity functions by means of an isolation boundary (implemented via partitions and domains) controlling access to, and protecting the integrity of, the hardware, software, and firmware that perform those security functions. The information system maintains a separate execution domain (e.g., address space) for each executing process.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001089",
"ruleFixText": "Configure the SharePoint server to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.\n\nConfigure access to Central Administration to be allowed over a management (OOB) network.\n\nConfigure Central Administration on a server that resides within the internal network (not on a server in the DMZ).\n\nConfigure management access (i.e., remote desktop access and local server access) so that it occurs only via a management network (OOB) and not over a production network.",
"ruleFixId": "F-24922r430841_fix",
"ruleCheckSystem": "C-24934r430840_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers are implemented.\n\nCheck the network location of the Central Administration server.\n\nIf the server resides in the DMZ, this is a finding.\n\nAttempt to access Central Administration without first connecting to a management network VPN.\n\nIf Central Administration can be accessed over a production network, this is a finding.\n\nAttempt to connect directly to a SharePoint server (i.e., via remote desktop) without first connecting to a management network VPN.\n\nIf a remote desktop session can be established via a production network, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19403,
"benchmarkId": 379,
"groupId": "V-223262",
"title": "SRG-APP-000440",
"description": "",
"ruleId": "SV-223262r961635_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000135",
"ruleTitle": "SharePoint must employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission, unless the transmitted data is otherwise protected by alternative physical measures.",
"ruleVulnDiscussion": "Preventing the disclosure of transmitted information requires that applications take measures to employ some form of cryptographic mechanism in order to protect the information during transmission. This is usually achieved through the use of Transport Layer Security (TLS), SSL VPN, or IPSEC tunnel.\n\nAlternative physical protection measures include Protected Distribution Systems (PDS). PDS are used to transmit unencrypted classified NSI through an area of lesser classification or control. Inasmuch as the classified NSI is unencrypted, the PDS must provide adequate electrical, electromagnetic, and physical safeguards to deter exploitation. Refer to NSTSSI No. 7003 for additional details on a PDS.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-002421",
"ruleFixText": "Configure the SharePoint server to employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission, unless the transmitted data is otherwise protected by alternative physical measures.\n\nOpen IIS Manager.\n\nIn the Connections pane, expand Sites.\n\nClick the Web Application site.\n\nIn the Actions pane, click Bindings.\n\nIn the Site Bindings window, click Add.\n\nIn the Add Site Binding window, change Type to https, and select the site's SSL certificate.\n\nClick OK, and then click Close.",
"ruleFixId": "F-24923r430844_fix",
"ruleCheckSystem": "C-24935r430843_chk",
"ruleCheckContent": "Review the SharePoint server to ensure cryptographic mechanisms preventing the unauthorized disclosure of information during transmission are employed, unless the transmitted data is otherwise protected by alternative physical measures.\n\nIn SharePoint Central Administration, click Application Management.\n\nOn the Application Management page, in the Web Applications list, click Manage web applications.\n\nOn the Web Applications Management page, verify that each Web Application URL begins with https.\n\nIf the URL does not begin with https, this is a finding.\n\nIf SharePoint communications between all components and clients are protected by alternative physical measures that have been approved by the AO, this is not a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19404,
"benchmarkId": 379,
"groupId": "V-223263",
"title": "SRG-APP-000340",
"description": "",
"ruleId": "SV-223263r961353_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000140",
"ruleTitle": "SharePoint must prevent non-privileged users from circumventing malicious code protection capabilities.",
"ruleVulnDiscussion": "Malicious code protection software must be protected to prevent a non-privileged user or malicious piece of software from disabling the protection mechanism. A common tactic of malware is to identify the type of malicious code protection software running on the system and deactivate it. Malicious code includes viruses, worms, Trojan horses, and Spyware.\n\nExamples include the capability for non-administrative users to turn off or otherwise disable anti-virus.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-002235",
"ruleFixText": "Configure the SharePoint server to prevent non-privileged users from circumventing malicious code protection capabilities.\n\nNavigate to Central Administration.\n\nClick \"Manage web applications\".\n\nSelect the web application by clicking its name.\n\nSelect \"Blocked File Types\" from the ribbon.\n\nAdd file types that are defined in the SSP but not in the list of blocked file types.\n\nClick \"Ok\".\n\nRepeat for each web application that has findings.",
"ruleFixId": "F-24924r430847_fix",
"ruleCheckSystem": "C-24936r430846_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure non-privileged users are prevented from circumventing malicious code protection capabilities.\n\nConfirm that the list of blocked file types configured in Central Administration matches the \"blacklist\" document in the application's SSP. See TechNet for default file types that are blocked: http://technet.microsoft.com/en-us/library/cc262496.aspx\n\nNavigate to Central Administration.\n\nClick \"Manage web applications\".\n\nSelect the web application by clicking its name.\n\nSelect \"Blocked File Types\" from the ribbon.\n\nCompare the list of blocked file types to those listed in the SSP. If the SSP has file types that are not in the blocked file types list, this is a finding.\n\nRepeat check for each web application.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19405,
"benchmarkId": 379,
"groupId": "V-223264",
"title": "SRG-APP-000179",
"description": "",
"ruleId": "SV-223264r961050_rule",
"ruleWeight": "10.0",
"ruleSeverity": "high",
"ruleVersion": "SP13-00-000145",
"ruleTitle": "SharePoint must use mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.",
"ruleVulnDiscussion": "Certain encryption types are no longer considered secure. This setting configures a minimum encryption type for SharePoint. Different versions of the Windows Server OS and versions of SharePoint will have different suites available.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000803",
"ruleFixText": "Configure the SharePoint server to use mechanisms for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.\n\nOpen MMC.\n\nClick “File”, “Add/Remove Snap-in”, and “add Group Policy Object Editor”.\n\nEnter a name for the Group Policy Object, or accept the default.\n\nClick “Finish”.\n\nClick “OK”.\n\nNavigate to Computer Policy >> Computer Configuration >> Administrative Templates >> Network >> SSL Configuration Settings.\n\nRight-click “SSL Configuration Settings”, click “SSL Cipher Suite Order”, and then click “Edit”.\n\nIn the “SSL Cipher Suite Order” dialog box, select \"Enabled\".\n\nUnder “Options”, in the “SSL Cipher Suites” text box, enter desired cipher suites that are not DES or RC4.\n\nClick “OK”.",
"ruleFixId": "F-24925r821367_fix",
"ruleCheckSystem": "C-24937r821366_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure mechanisms are used for authentication to a cryptographic module that meet the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for such authentication.\n\nOpen Registry Editor.\n\nNavigate to \"HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Cryptography\\Configuration\\SSL\\00010002\".\n\nIf the REG_SZ \"Functions\" value does not exist, this is a finding.\n\nOpen the REG_SZ \"Functions\" value.\n\nIf any DES or RC4 cipher suites exist in the text string, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19406,
"benchmarkId": 379,
"groupId": "V-223265",
"title": "SRG-APP-000212",
"description": "",
"ruleId": "SV-223265r987634_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000150",
"ruleTitle": "The SharePoint Central Administration site must not be accessible from Extranet or Internet connections.",
"ruleVulnDiscussion": "SharePoint must prevent the presentation of information system management-related functionality at an interface utilized by general, (i.e., non-privileged), users. \n\nThe Central Administrator is an application used to manage SharePoint system settings and the settings of the web applications running under SharePoint. The Central Administrator application should both be protected using a defense-in-depth approach. Regular users should not be able to access the Central Administrator as the first line of defense. The second line of defense is regular users do not have user ids defined in the Central Administration application.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001083",
"ruleFixText": "Configure the SharePoint Central Administration site to not be accessible from Extranet or Internet connections.\n\nBlock outside Central Administrator access.\n\nUse an IIS IP address restrictions, firewall, or other filtering solutions to limit access to Central Administration site.",
"ruleFixId": "F-24926r430853_fix",
"ruleCheckSystem": "C-24938r430852_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure Central Administration site is not accessible from Extranet or Internet connections.\n\nCheck outside access to Central Administration.\n\nOn an administrative work station, open Central Administration and make note of the URL (i.e., http://sharepointserver:7040).\n\nTry to open the Central Administration application on a regular user's workstation. Open a Web browser and type in the URL to Central Administration.\n\nIf the Central Administration can be opened, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19407,
"benchmarkId": 379,
"groupId": "V-223266",
"title": "SRG-APP-000039",
"description": "",
"ruleId": "SV-223266r960804_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000155",
"ruleTitle": "For environments requiring an Internet-facing capability, the SharePoint application server upon which Central Administration is installed, must not be installed in the DMZ.",
"ruleVulnDiscussion": "Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to the information. \n\nSharePoint installed Central Administrator is a powerful management tool used to administer the farm. This server should be installed on a trusted network segment. This server should also be used to run services rather than user-oriented web applications.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-001414",
"ruleFixText": "For environments requiring an Internet-facing capability, remove the SharePoint Central Administration application server upon which Central Administration is installed from the DMZ.",
"ruleFixId": "F-24927r430856_fix",
"ruleCheckSystem": "C-24939r430855_chk",
"ruleCheckContent": "For environments requiring an Internet-facing capability, ensure the SharePoint Central Administration application server is not in the DMZ.\n\nInspect the logical location of the server farm web front end servers.\n\nVerify the Central Administration site is not installed on a server located in a DMZ or other publicly accessible segment of the network.\n\nIf Central Administrator is installed on a publicly facing SharePoint server, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19408,
"benchmarkId": 379,
"groupId": "V-223267",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223267r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000160",
"ruleTitle": "The SharePoint farm service account (database access account) must be configured with minimum privileges in Active Directory (AD).",
"ruleVulnDiscussion": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action. \n\nThis requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts. \nThis policy limits the Farm Account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the \"Database Access\" account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint farm service account (database access account) with minimum privileges in Active Directory (AD).\n\nEnsure the Setup User domain user has minimum permissions in Active Directory. \n- Using the AD DS console, navigate to “Active Directory Users and Computers” >> Users.\n- Double click on the account to view the account properties.\n- Select the “Members of” tab and configure the farm service account is a member of the Domain Users group. Remove any other group membership from the account.\n- Select the other tabs in this area and remove any services or permissions configured for this account.",
"ruleFixId": "F-24928r430859_fix",
"ruleCheckSystem": "C-24940r430858_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the farm service account (database access account) is configured with minimum privileges in Active Directory (AD).\n\n- Verify the account has least privilege in Active Directory.\n- Navigate to “Active Directory Users and Computers” >> Users.\n- Double click on the account to view the account properties.\n- Select the “Members of” tab and verify this account is a member of the Domain Users group only.\n- Select the other tabs in this area to verify no other services or permissions are configured for this account.\n\nIf the farm service account is a member of other groups other than Domain Users, this is a finding.\n\nIf the Setup User account has unneeded permissions or services assigned, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19409,
"benchmarkId": 379,
"groupId": "V-223268",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223268r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000165",
"ruleTitle": "The SharePoint farm service account (database access account) must be configured with minimum privileges on the SQL server.",
"ruleVulnDiscussion": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action. \n\nThis requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts. \nThis policy limits the Farm Account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the \"Database Access\" account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint farm service account (database access account) with minimum privileges on the SQL server.\n\nConfigure the account on each SQL server in the farm.\n- Launch the SQL Server Management Console and navigate to Security >> Logins. \n- Select the SharePoint farm service account.\n- Click on Server Roles.\n- Ensure only public, dbcreator, and securityadmin roles are checked.\n- Remove checks from all other roles.",
"ruleFixId": "F-24929r430862_fix",
"ruleCheckSystem": "C-24941r430861_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the farm service account (database access account) is configured with minimum privileges on the SQL server.\n\n- Launch the SQL Server Management Console and navigate to Security >> Logins. \n- Select the SharePoint farm service account. \n- Click on \"Server Roles\" and verify only public, dbcreator, and securityadmin are checked.\n- Click on \"User Mapping\" and verify that the farm account is a member of the public and db_owner role on each SharePoint database.\n\nOtherwise, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19410,
"benchmarkId": 379,
"groupId": "V-223269",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223269r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000170",
"ruleTitle": "The SharePoint setup account must be configured with the minimum privileges in Active Directory.",
"ruleVulnDiscussion": "Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action. \n\nThis requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts.\n \nThis policy limits the setup account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the \"Database Access\" account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint setup account to be configured with the minimum privileges in Active Directory.\n\nEnsure the Setup User domain user has minimum permissions in Active Directory. \n- Using the AD DS console, navigate to “Active Directory Users and Computers” >> Users.\n- Double click on the account to view the account properties.\n- Select the “Members of” tab and configure the Setup user account is a member of the Domain Users group. Remove any other group membership from the account.\n- Select the other tabs in this area and remove any services or permissions configured for this account.",
"ruleFixId": "F-24930r430865_fix",
"ruleCheckSystem": "C-24942r430864_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure the setup account is configured with the minimum privileges in Active Directory.\n\nVerify the account has least privilege in Active Directory.\n- Navigate to “Active Directory Users and Computers” >> Users.\n- Double click on the account to view the account properties.\n- Select the “Members of” tab and verify this account is a member of the Domain Users group only.\n- Select the other tabs in this area to verify no other services or permissions are configured for this account.\n\nIf the Setup User account is a member of other groups other than Domain Users, this is a finding.\n\nIf the Setup User account has unneeded permissions or services assigned, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19412,
"benchmarkId": 379,
"groupId": "V-223272",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223272r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "low",
"ruleVersion": "SP13-00-000185",
"ruleTitle": "A secondary SharePoint site collection administrator must be defined when creating a new site collection.",
"ruleVulnDiscussion": "If a site reaches its maximum size, users will be denied access until an administrator fixes the problem. Having a secondary administrator reduces the risk of having a Denial-of-Service on a site. If the site reaches its maximum size, the secondary administrator can fix the problem if the primary administrator is not available. In some situations, having a secondary site administrator could be inappropriate for reasons of control or confidentiality.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure a secondary SharePoint site collection administrator when creating a new site collection.\n\nLog on to SharePoint Central Administration as a member of the Farm Administration Group.\n\nClick on \"Application Management\".\n\nSelect \"Site Collections\" >> Change Site Collections Administrator.\n\nFor each site, define a Secondary Site Collection Administrator.\n\nSelect \"OK\".",
"ruleFixId": "F-24933r430874_fix",
"ruleCheckSystem": "C-24945r430873_chk",
"ruleCheckContent": "Review the SharePoint server to ensure a secondary site collection administrator is defined when creating a new site collection.\n\nLog on to SharePoint Central Administration as a member of the Farm Administration Group.\n\nClick on \"Application Management\".\n\nSelect \"Site Collections\" >> Change Site Collections Administrator.\n\nFor each Site Collections, review Secondary Site Collection Administrator.\n\nIf Secondary Site Collection Administrator is not defined, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19413,
"benchmarkId": 379,
"groupId": "V-223273",
"title": "SRG-APP-000142",
"description": "",
"ruleId": "SV-223273r1043177_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000190",
"ruleTitle": "When configuring SharePoint Central Administration, the port number selected must comply with DoD Ports and Protocol Management (PPSM) program requirements.",
"ruleVulnDiscussion": "During the installation of Microsoft SharePoint, the Central Administration Web site is established on a randomly-assigned TCP port by default. Allowing a randomly-assigned default may result in use of a port which violates DoD policy or conflicts with ports already in use. Use of certain well-known ports may also result in slow operational response or expose the application to known denial of service attacks.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000382",
"ruleFixText": "Configure the SharePoint Central Administration port number selected to comply with DoD Ports and Protocol Management (PPSM) program requirements.\n\nOpen the SharePoint Management Shell (Start >> All Programs >> Microsoft SharePoint Products >> SharePoint Management Shell). \n\nChange the port number to a PPS-approved port that does not conflict with existing port usage using the following command: \nSet -SPCentralAdministration -Port \n\nPress \"Enter\" to save.",
"ruleFixId": "F-24934r430877_fix",
"ruleCheckSystem": "C-24946r430876_chk",
"ruleCheckContent": "Review the SharePoint server Central Administration configuration to ensure the port number selected complies with DoD Ports and Protocol Management (PPSM) program requirements.\n\nOpen the SharePoint Management Shell (Start >> All Programs >> Microsoft SharePoint Products >> SharePoint Management Shell). \n\nType the following command at the PowerShell prompt:\nGet-SPWebApplication -IncludeCentralAdministration\n\nFind the entry for the Central Administration web application and verify the port listed in the URL column is allowed by the DoD PPSM policy.\n\nIf the port number is not allowed in accordance with DoD PPSM policy, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19414,
"benchmarkId": 379,
"groupId": "V-223274",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223274r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000195",
"ruleTitle": "SharePoint-specific malware (i.e. anti-virus) protection software must be integrated and configured.",
"ruleVulnDiscussion": "Configuring anti-virus settings ensures documents will be scanned for viruses upon download from and upload to the SharePoint server. Anti-virus settings are not configured by default, therefore leaving the documents downloaded from or uploaded to SharePoint open to potential viruses.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure and integrate SharePoint-specific malware (i.e. anti-virus) protection software on the SharePoint server.\n\nInstall and configure anti-virus package.\n\nInstall a SharePoint Server 2010-specific antivirus package. \n\nLog in to Central Administration.\n\nNavigate to Operations >> Security Configuration.\n\nSelect Anti-virus.\n\nCheck the following boxes:\n- Scan documents on upload.\n- Scan documents on download.\n- Attempt to clean infected documents.\n\nSelect \"OK\".",
"ruleFixId": "F-24935r430880_fix",
"ruleCheckSystem": "C-24947r430879_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure SharePoint-specific malware (i.e. anti-virus) protection software is integrated and configured.\n\nLog on to Central Administrator.\n\nNavigate to Operations >> Security Configuration.\n\nSelect Anti-virus.\n\nIf any of the following boxes are unselected, this is a finding:\n- Scan documents on upload.\n- Scan documents on download.\n- Attempt to clean infected documents.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
},
{
"id": 19415,
"benchmarkId": 379,
"groupId": "V-223275",
"title": "SRG-APP-000516",
"description": "",
"ruleId": "SV-223275r961863_rule",
"ruleWeight": "10.0",
"ruleSeverity": "medium",
"ruleVersion": "SP13-00-000205",
"ruleTitle": "SharePoint server access to the Online Web Part Gallery must be configured for limited access.",
"ruleVulnDiscussion": "Web Part galleries are groupings of Web Parts. There are four Web Part galleries: Closed Web Parts, Site Name Gallery, Server Gallery, and Online Gallery. The Online Gallery is a collection of Microsoft MSNBC Web Parts located on the Internet. Allowing users to access the Online Web Part Gallery causes a significant performance hit on the server, due to the server attempting to connect to the MSNBC online gallery. This could result in a Denial-of-Service. The Online Gallery could contain Web Parts from unknown third parties, which could increase the risk of a malicious code execution attack. Preventing users from accessing the Online Web Part Gallery decreases the system's attack surface.",
"ruleFalsePositives": "",
"ruleFalseNegatives": "",
"ruleDocumentable": "false",
"ruleMitigations": "",
"ruleIdent": "CCI-000366",
"ruleFixText": "Configure the SharePoint server for limited access to the Online Web Part Gallery.\n\nEnable the \"Prevents users from accessing the Online Web Part Gallery, and helps to improve security and performance\" option for each web application. \n\nLog on to Central Administration.\n\nNavigate to the Security page.\n\nClick on \"Manage web part security\".\n\nFor each web application in the web application section, perform the following: \n-Select the correct web application in the web application section.\n-Select the \"Prevents users from accessing the Online Web Part Gallery, and helps to improve security and performance\" option in the Online Web Part Gallery section.\n\nSelect \"OK\".",
"ruleFixId": "F-24936r430883_fix",
"ruleCheckSystem": "C-24948r430882_chk",
"ruleCheckContent": "Review the SharePoint server configuration to ensure access to the online web part gallery is configured for limited access.\n\nLog on to Central Administration.\n\nNavigate to the Security page.\n\nClick on \"Manage web part security\".\n\nFor each web application in the web application section, perform the following: \n-Select the correct web application in the web application section.\n-Verify \"Prevents users from accessing the Online Web Part Gallery, and helps to improve security and performance\" option in the Online Web Part Gallery section is selected.\n\nIf the \"Prevents users from accessing the Online Web Part Gallery, and helps to improve security and performance\" option in the Online Web Part Gallery section is not checked, this is a finding.",
"createdAt": "2025-10-21T11:31:04.256Z",
"updatedAt": "2025-10-21T11:31:04.256Z"
}
],
"profiles": [
{
"id": 3344,
"benchmarkId": 379,
"profileId": "MAC-1_Classified",
"title": "I - Mission Critical Classified",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3345,
"benchmarkId": 379,
"profileId": "MAC-1_Public",
"title": "I - Mission Critical Public",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3346,
"benchmarkId": 379,
"profileId": "MAC-1_Sensitive",
"title": "I - Mission Critical Sensitive",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3347,
"benchmarkId": 379,
"profileId": "MAC-2_Classified",
"title": "II - Mission Support Classified",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3348,
"benchmarkId": 379,
"profileId": "MAC-2_Public",
"title": "II - Mission Support Public",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3349,
"benchmarkId": 379,
"profileId": "MAC-2_Sensitive",
"title": "II - Mission Support Sensitive",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3350,
"benchmarkId": 379,
"profileId": "MAC-3_Classified",
"title": "III - Administrative Classified",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3351,
"benchmarkId": 379,
"profileId": "MAC-3_Public",
"title": "III - Administrative Public",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
},
{
"id": 3352,
"benchmarkId": 379,
"profileId": "MAC-3_Sensitive",
"title": "III - Administrative Sensitive",
"description": "",
"createdAt": "2025-10-21T11:31:05.055Z",
"updatedAt": "2025-10-21T11:31:05.055Z"
}
]
}