REFERENCE

The control list behind the mapping

The Enterprise page maps seven public standards to the domains a behavioral comparison covers. Behind those standards are individual controls. This page lists the ones pulled from the publishers' own machine-readable sources: OWASP ASVS 4.0.3, CWE, and NIST SP 800-53 revision 5. Each entry carries a provisional classification. Shows means a behavioral comparison demonstrates the control directly. Supports means the comparison contributes evidence without being the whole answer. A review pass of these classifications is in progress. This list is illustrative, not a compliance certification.

749 controls total · 128 OWASP ASVS · 75 CWE · 546 NIST SP 800-53r5 · 262 shows · 487 supports

OWASP ASVS 4.0.3 (128)

IDRequirementDomainClassification
V3.1.1Verify the application never reveals session tokens in URL parameters.session managementshows
V3.2.1Verify the application generates a new session token on user authentication. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))session managementshows
V3.2.2Verify that session tokens possess at least 64 bits of entropy. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))session managementshows
V3.2.3Verify the application only stores session tokens in the browser using secure methods such as appropriately secured cookies (see section 3.4) or HTML 5 session session managementshows
V3.2.4Verify that session tokens are generated using approved cryptographic algorithms. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))session managementshows
V3.3.1Verify that logout and expiration invalidate the session token, such that the back button or a downstream relying party does not resume an authenticated sessionsession managementshows
V3.3.2If authenticators permit users to remain logged in, verify that re-authentication occurs periodically both when actively used or after an idle period. ([C6](httsession managementshows
V3.3.3Verify that the application gives the option to terminate all other active sessions after a successful password change (including change via password reset/recosession managementshows
V3.3.4Verify that users are able to view and (having re-entered login credentials) log out of any or all currently active sessions and devices.session managementshows
V3.4.1Verify that cookie-based session tokens have the 'Secure' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))session managementshows
V3.4.2Verify that cookie-based session tokens have the 'HttpOnly' attribute set. ([C6](https://owasp.org/www-project-proactive-controls/#div-numbering))session managementshows
V3.4.3Verify that cookie-based session tokens utilize the 'SameSite' attribute to limit exposure to cross-site request forgery attacks. ([C6](https://owasp.org/www-prsession managementshows
V3.4.4Verify that cookie-based session tokens use the "__Host-" prefix so cookies are only sent to the host that initially set the cookie.session managementshows
V3.4.5Verify that if the application is published under a domain name with other applications that set or use session cookies that might disclose the session cookies,session managementshows
V3.5.1Verify the application allows users to revoke OAuth tokens that form trust relationships with linked applications.session managementsupports
V3.5.2Verify the application uses session tokens rather than static API secrets and keys, except with legacy implementations.session managementshows
V3.5.3Verify that stateless session tokens use digital signatures, encryption, and other countermeasures to protect against tampering, enveloping, replay, null ciphersession managementshows
V3.6.1Verify that Relying Parties (RPs) specify the maximum authentication time to Credential Service Providers (CSPs) and that CSPs re-authenticate the user if they session managementsupports
V3.6.2Verify that Credential Service Providers (CSPs) inform Relying Parties (RPs) of the last authentication event, to allow RPs to determine if they need to re-authsession managementshows
V3.7.1Verify the application ensures a full, valid login session or requires re-authentication or secondary verification before allowing any sensitive transactions orsession managementshows
V4.1.1Verify that the application enforces access control rules on a trusted service layer, especially if client-side access control is present and could be bypassed.access controlsupports
V4.1.2Verify that all user and data attributes and policy information used by access controls cannot be manipulated by end users unless specifically authorized.access controlshows
V4.1.3Verify that the principle of least privilege exists - users should only be able to access functions, data files, URLs, controllers, services, and other resourceaccess controlshows
V4.1.4[DELETED, DUPLICATE OF 4.1.3]access controlsupports
V4.1.5Verify that access controls fail securely including when an exception occurs. ([C10](https://owasp.org/www-project-proactive-controls/#div-numbering))access controlshows
V4.2.1Verify that sensitive data and APIs are protected against Insecure Direct Object Reference (IDOR) attacks targeting creation, reading, updating and deletion of access controlshows
V4.2.2Verify that the application or framework enforces a strong anti-CSRF mechanism to protect authenticated functionality, and effective anti-automation or anti-CSRaccess controlsupports
V4.3.1Verify administrative interfaces use appropriate multi-factor authentication to prevent unauthorized use.access controlshows
V4.3.2Verify that directory browsing is disabled unless deliberately desired. Additionally, applications should not allow discovery or disclosure of file or directoryaccess controlsupports
V4.3.3Verify the application has additional authorization (such as step up or adaptive authentication) for lower value systems, and / or segregation of duties for higaccess controlshows
V5.1.1Verify that the application has defenses against HTTP parameter pollution attacks, particularly if the application framework makes no distinction about the sourvalidation and encodingsupports
V5.1.2Verify that frameworks protect against mass parameter assignment attacks, or that the application has countermeasures to protect against unsafe parameter assignvalidation and encodingsupports
V5.1.3Verify that all input (HTML form fields, REST requests, URL parameters, HTTP headers, cookies, batch files, RSS feeds, etc) is validated using positive validativalidation and encodingsupports
V5.1.4Verify that structured data is strongly typed and validated against a defined schema including allowed characters, length and pattern (e.g. credit card numbers,validation and encodingsupports
V5.1.5Verify that URL redirects and forwards only allow destinations which appear on an allow list, or show a warning when redirecting to potentially untrusted contenvalidation and encodingsupports
V5.2.1Verify that all untrusted HTML input from WYSIWYG editors or similar is properly sanitized with an HTML sanitizer library or framework feature. ([C5](https://owvalidation and encodingsupports
V5.2.2Verify that unstructured data is sanitized to enforce safety measures such as allowed characters and length.validation and encodingsupports
V5.2.3Verify that the application sanitizes user input before passing to mail systems to protect against SMTP or IMAP injection.validation and encodingsupports
V5.2.4Verify that the application avoids the use of eval() or other dynamic code execution features. Where there is no alternative, any user input being included mustvalidation and encodingsupports
V5.2.5Verify that the application protects against template injection attacks by ensuring that any user input being included is sanitized or sandboxed.validation and encodingsupports
V5.2.6Verify that the application protects against SSRF attacks, by validating or sanitizing untrusted data or HTTP file metadata, such as filenames and URL input fievalidation and encodingsupports
V5.2.7Verify that the application sanitizes, disables, or sandboxes user-supplied Scalable Vector Graphics (SVG) scriptable content, especially as they relate to XSS validation and encodingsupports
V5.2.8Verify that the application sanitizes, disables, or sandboxes user-supplied scriptable or expression template language content, such as Markdown, CSS or XSL styvalidation and encodingsupports
V5.3.1Verify that output encoding is relevant for the interpreter and context required. For example, use encoders specifically for HTML values, HTML attributes, JavaSvalidation and encodingsupports
V5.3.2Verify that output encoding preserves the user's chosen character set and locale, such that any Unicode character point is valid and safely handled. ([C4](httpsvalidation and encodingsupports
V5.3.3Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM based XSS. ([C4](https://owavalidation and encodingshows
V5.3.4Verify that data selection or database queries (e.g. SQL, HQL, ORM, NoSQL) use parameterized queries, ORMs, entity frameworks, or are otherwise protected from dvalidation and encodingsupports
V5.3.5Verify that where parameterized or safer mechanisms are not present, context-specific output encoding is used to protect against injection attacks, such as the validation and encodingsupports
V5.3.6Verify that the application protects against JSON injection attacks, JSON eval attacks, and JavaScript expression evaluation. ([C4](https://owasp.org/www-projecvalidation and encodingsupports
V5.3.7Verify that the application protects against LDAP injection vulnerabilities, or that specific security controls to prevent LDAP injection have been implemented.validation and encodingshows
V5.3.8Verify that the application protects against OS command injection and that operating system calls use parameterized OS queries or use contextual command line ouvalidation and encodingsupports
V5.3.9Verify that the application protects against Local File Inclusion (LFI) or Remote File Inclusion (RFI) attacks.validation and encodingsupports
V5.3.10Verify that the application protects against XPath injection or XML injection attacks. ([C4](https://owasp.org/www-project-proactive-controls/#div-numbering))validation and encodingsupports
V5.4.1Verify that the application uses memory-safe string, safer memory copy and pointer arithmetic to detect or prevent stack, buffer, or heap overflows.validation and encodingshows
V5.4.2Verify that format strings do not take potentially hostile input, and are constant.validation and encodingsupports
V5.4.3Verify that sign, range, and input validation techniques are used to prevent integer overflows.validation and encodingshows
V5.5.1Verify that serialized objects use integrity checks or are encrypted to prevent hostile object creation or data tampering. ([C5](https://owasp.org/www-project-pvalidation and encodingshows
V5.5.2Verify that the application correctly restricts XML parsers to only use the most restrictive configuration possible and to ensure that unsafe features such as rvalidation and encodingsupports
V5.5.3Verify that deserialization of untrusted data is avoided or is protected in both custom code and third-party libraries (such as JSON, XML and YAML parsers).validation and encodingsupports
V5.5.4Verify that when parsing JSON in browsers or JavaScript-based backends, JSON.parse is used to parse the JSON document. Do not use eval() to parse JSON.validation and encodingsupports
V7.1.1Verify that the application does not log credentials or payment details. Session tokens should only be stored in logs in an irreversible, hashed form. ([C9, C10error handling and loggingshows
V7.1.2Verify that the application does not log other sensitive data as defined under local privacy laws or relevant security policy. ([C9](https://owasp.org/www-projeerror handling and loggingshows
V7.1.3Verify that the application logs security relevant events including successful and failed authentication events, access control failures, deserialization failurerror handling and loggingshows
V7.1.4Verify that each log event includes necessary information that would allow for a detailed investigation of the timeline when an event happens. ([C9](https://owaerror handling and loggingshows
V7.2.1Verify that all authentication decisions are logged, without storing sensitive session tokens or passwords. This should include requests with relevant metadata error handling and loggingshows
V7.2.2Verify that all access control decisions can be logged and all failed decisions are logged. This should include requests with relevant metadata needed for securerror handling and loggingshows
V7.3.1Verify that all logging components appropriately encode data to prevent log injection. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))error handling and loggingshows
V7.3.2[DELETED, DUPLICATE OF 7.3.1]error handling and loggingsupports
V7.3.3Verify that security logs are protected from unauthorized access and modification. ([C9](https://owasp.org/www-project-proactive-controls/#div-numbering))error handling and loggingshows
V7.3.4Verify that time sources are synchronized to the correct time and time zone. Strongly consider logging only in UTC if systems are global to assist with post-incerror handling and loggingshows
V7.4.1Verify that a generic message is shown when an unexpected or security sensitive error occurs, potentially with a unique ID which support personnel can use to inerror handling and loggingshows
V7.4.2Verify that exception handling (or a functional equivalent) is used across the codebase to account for expected and unexpected error conditions. ([C10](https://error handling and loggingshows
V7.4.3Verify that a "last resort" error handler is defined which will catch all unhandled exceptions. ([C10](https://owasp.org/www-project-proactive-controls/#div-numerror handling and loggingshows
V8.1.1Verify the application protects sensitive data from being cached in server components such as load balancers and application caches.data protectionsupports
V8.1.2Verify that all cached or temporary copies of sensitive data stored on the server are protected from unauthorized access or purged/invalidated after the authoridata protectionshows
V8.1.3Verify the application minimizes the number of parameters in a request, such as hidden fields, Ajax variables, cookies and header values.data protectionsupports
V8.1.4Verify the application can detect and alert on abnormal numbers of requests, such as by IP, user, total per hour or day, or whatever makes sense for the applicadata protectionsupports
V8.1.5Verify that regular backups of important data are performed and that test restoration of data is performed.data protectionsupports
V8.1.6Verify that backups are stored securely to prevent data from being stolen or corrupted.data protectionshows
V8.2.1Verify the application sets sufficient anti-caching headers so that sensitive data is not cached in modern browsers.data protectionsupports
V8.2.2Verify that data stored in browser storage (such as localStorage, sessionStorage, IndexedDB, or cookies) does not contain sensitive data.data protectionshows
V8.2.3Verify that authenticated data is cleared from client storage, such as the browser DOM, after the client or session is terminated.data protectionshows
V8.3.1Verify that sensitive data is sent to the server in the HTTP message body or headers, and that query string parameters from any HTTP verb do not contain sensitidata protectionshows
V8.3.2Verify that users have a method to remove or export their data on demand.data protectionsupports
V8.3.3Verify that users are provided clear language regarding collection and use of supplied personal information and that users have provided opt-in consent for the data protectionsupports
V8.3.4Verify that all sensitive data created and processed by the application has been identified, and ensure that a policy is in place on how to deal with sensitive data protectionsupports
V8.3.5Verify accessing sensitive data is audited (without logging the sensitive data itself), if the data is collected under relevant data protection directives or whdata protectionshows
V8.3.6Verify that sensitive information contained in memory is overwritten as soon as it is no longer required to mitigate memory dumping attacks, using zeroes or randata protectionsupports
V8.3.7Verify that sensitive or private information that is required to be encrypted, is encrypted using approved algorithms that provide both confidentiality and intedata protectionsupports
V8.3.8Verify that sensitive personal information is subject to data retention classification, such that old or out of date data is deleted automatically, on a scheduldata protectionsupports
V11.1.1Verify that the application will only process business logic flows for the same user in sequential step order and without skipping steps.business logicshows
V11.1.2Verify that the application will only process business logic flows with all steps being processed in realistic human time, i.e. transactions are not submitted tbusiness logicshows
V11.1.3Verify the application has appropriate limits for specific business actions or transactions which are correctly enforced on a per user basis.business logicshows
V11.1.4Verify that the application has anti-automation controls to protect against excessive calls such as mass data exfiltration, business logic requests, file uploadbusiness logicshows
V11.1.5Verify the application has business logic limits or validation to protect against likely business risks or threats, identified using threat modeling or similar business logicshows
V11.1.6Verify that the application does not suffer from "Time Of Check to Time Of Use" (TOCTOU) issues or other race conditions for sensitive operations.business logicsupports
V11.1.7Verify that the application monitors for unusual events or activity from a business logic perspective. For example, attempts to perform actions out of order or business logicshows
V11.1.8Verify that the application has configurable alerting when automated attacks or unusual activity is detected.business logicsupports
V12.1.1Verify that the application will not accept large files that could fill up storage or cause a denial of service.files and resourcessupports
V12.1.2Verify that the application checks compressed files (e.g. zip, gz, docx, odt) against maximum allowed uncompressed size and against maximum number of files befofiles and resourcessupports
V12.1.3Verify that a file size quota and maximum number of files per user is enforced to ensure that a single user cannot fill up the storage with too many files, or efiles and resourcessupports
V12.2.1Verify that files obtained from untrusted sources are validated to be of expected type based on the file's content.files and resourcessupports
V12.3.1Verify that user-submitted filename metadata is not used directly by system or framework filesystems and that a URL API is used to protect against path traversafiles and resourcesshows
V12.3.2Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure, creation, updating or removal of local files (LFI).files and resourcesshows
V12.3.3Verify that user-submitted filename metadata is validated or ignored to prevent the disclosure or execution of remote files via Remote File Inclusion (RFI) or Sfiles and resourcesshows
V12.3.4Verify that the application protects against Reflective File Download (RFD) by validating or ignoring user-submitted filenames in a JSON, JSONP, or URL parametefiles and resourcessupports
V12.3.5Verify that untrusted file metadata is not used directly with system API or libraries, to protect against OS command injection.files and resourcesshows
V12.3.6Verify that the application does not include and execute functionality from untrusted sources, such as unverified content distribution networks, JavaScript librfiles and resourcessupports
V12.4.1Verify that files obtained from untrusted sources are stored outside the web root, with limited permissions.files and resourcessupports
V12.4.2Verify that files obtained from untrusted sources are scanned by antivirus scanners to prevent upload and serving of known malicious content.files and resourcesshows
V12.5.1Verify that the web tier is configured to serve only files with specific file extensions to prevent unintentional information and source code leakage. For exampfiles and resourcesshows
V12.5.2Verify that direct requests to uploaded files will never be executed as HTML/JavaScript content.files and resourcessupports
V12.6.1Verify that the web or application server is configured with an allow list of resources or systems to which the server can send requests or load data/files fromfiles and resourcessupports
V13.1.1Verify that all application components use the same encodings and parsers to avoid parsing attacks that exploit different URI or file parsing behavior that coulAPI and web servicesupports
V13.1.2[DELETED, DUPLICATE OF 4.3.1]API and web servicesupports
V13.1.3Verify API URLs do not expose sensitive information, such as the API key, session tokens etc.API and web serviceshows
V13.1.4Verify that authorization decisions are made at both the URI, enforced by programmatic or declarative security at the controller or router, and at the resource API and web serviceshows
V13.1.5Verify that requests containing unexpected or missing content types are rejected with appropriate headers (HTTP response status 406 Unacceptable or 415 UnsupporAPI and web servicesupports
V13.2.1Verify that enabled RESTful HTTP methods are a valid choice for the user or action, such as preventing normal users using DELETE or PUT on protected API or resoAPI and web serviceshows
V13.2.2Verify that JSON schema validation is in place and verified before accepting input.API and web servicesupports
V13.2.3Verify that RESTful web services that utilize cookies are protected from Cross-Site Request Forgery via the use of at least one or more of the following: doubleAPI and web servicesupports
V13.2.4[DELETED, DUPLICATE OF 11.1.4]API and web servicesupports
V13.2.5Verify that REST services explicitly check the incoming Content-Type to be the expected one, such as application/xml or application/json.API and web servicesupports
V13.2.6Verify that the message headers and payload are trustworthy and not modified in transit. Requiring strong encryption for transport (TLS only) may be sufficient API and web servicesupports
V13.3.1Verify that XSD schema validation takes place to ensure a properly formed XML document, followed by validation of each input field before any processing of thatAPI and web servicesupports
V13.3.2Verify that the message payload is signed using WS-Security to ensure reliable transport between client and service.API and web servicesupports
V13.4.1Verify that a query allow list or a combination of depth limiting and amount limiting is used to prevent GraphQL or data layer expression Denial of Service (DoSAPI and web serviceshows
V13.4.2Verify that GraphQL or other data layer authorization logic should be implemented at the business logic layer instead of the GraphQL layer.API and web serviceshows

CWE v4.20 (75)

IDRequirementDomainClassification
CWE-1004Sensitive Cookie Without 'HttpOnly' Flagweakness classshows
CWE-116Improper Encoding or Escaping of Outputweakness classshows
CWE-117Improper Output Neutralization for Logsweakness classshows
CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')weakness classshows
CWE-1275Sensitive Cookie with Improper SameSite Attributeweakness classshows
CWE-134Use of Externally-Controlled Format Stringweakness classshows
CWE-138Improper Neutralization of Special Elementsweakness classshows
CWE-147Improper Neutralization of Input Terminatorsweakness classshows
CWE-159Improper Handling of Invalid Use of Special Elementsweakness classshows
CWE-176Improper Handling of Unicode Encodingweakness classshows
CWE-190Integer Overflow or Wraparoundweakness classshows
CWE-20Improper Input Validationweakness classshows
CWE-200Exposure of Sensitive Information to an Unauthorized Actorweakness classshows
CWE-210Self-generated Error Message Containing Sensitive Informationweakness classshows
CWE-212Improper Removal of Sensitive Information Before Storage or Transferweakness classshows
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')weakness classshows
CWE-226Sensitive Information in Resource Not Removed Before Reuseweakness classshows
CWE-233Improper Handling of Parametersweakness classshows
CWE-235Improper Handling of Extra Parametersweakness classshows
CWE-285Improper Authorizationweakness classshows
CWE-290Authentication Bypass by Spoofingweakness classshows
CWE-306Missing Authentication for Critical Functionweakness classshows
CWE-319Cleartext Transmission of Sensitive Informationweakness classshows
CWE-327Use of a Broken or Risky Cryptographic Algorithmweakness classshows
CWE-331Insufficient Entropyweakness classshows
CWE-345Insufficient Verification of Data Authenticityweakness classshows
CWE-352Cross-Site Request Forgery (CSRF)weakness classshows
CWE-367Time-of-check Time-of-use (TOCTOU) Race Conditionweakness classshows
CWE-384Session Fixationweakness classshows
CWE-390Detection of Error Condition Without Actionweakness classshows
CWE-400Uncontrolled Resource Consumptionweakness classshows
CWE-409Improper Handling of Highly Compressed Data (Data Amplification)weakness classshows
CWE-419Unprotected Primary Channelweakness classshows
CWE-431Missing Handlerweakness classshows
CWE-434Unrestricted Upload of File with Dangerous Typeweakness classshows
CWE-436Interpretation Conflictweakness classshows
CWE-502Deserialization of Untrusted Dataweakness classshows
CWE-509Replicating Malicious Code (Virus or Worm)weakness classshows
CWE-524Use of Cache Containing Sensitive Informationweakness classshows
CWE-525Use of Web Browser Cache Containing Sensitive Informationweakness classshows
CWE-532Insertion of Sensitive Information into Log Fileweakness classshows
CWE-539Use of Persistent Cookies Containing Sensitive Informationweakness classshows
CWE-544Missing Standardized Error Handling Mechanismweakness classshows
CWE-548Exposure of Information Through Directory Listingweakness classshows
CWE-552Files or Directories Accessible to External Partiesweakness classshows
CWE-598Use of HTTP Request With Sensitive Query Stringweakness classshows
CWE-601URL Redirection to Untrusted Site ('Open Redirect')weakness classshows
CWE-602Client-Side Enforcement of Server-Side Securityweakness classshows
CWE-611Improper Restriction of XML External Entity Referenceweakness classshows
CWE-613Insufficient Session Expirationweakness classshows
CWE-614Sensitive Cookie in HTTPS Session Without 'Secure' Attributeweakness classshows
CWE-639Authorization Bypass Through User-Controlled Keyweakness classshows
CWE-641Improper Restriction of Names for Files and Other Resourcesweakness classshows
CWE-643Improper Neutralization of Data within XPath Expressions ('XPath Injection')weakness classshows
CWE-650Trusting HTTP Permission Methods on the Server Sideweakness classshows
CWE-73External Control of File Name or Pathweakness classshows
CWE-732Incorrect Permission Assignment for Critical Resourceweakness classshows
CWE-754Improper Check for Unusual or Exceptional Conditionsweakness classshows
CWE-770Allocation of Resources Without Limits or Throttlingweakness classshows
CWE-778Insufficient Loggingweakness classshows
CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')weakness classshows
CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')weakness classshows
CWE-798Use of Hard-coded Credentialsweakness classshows
CWE-799Improper Control of Interaction Frequencyweakness classshows
CWE-829Inclusion of Functionality from Untrusted Control Sphereweakness classshows
CWE-830Inclusion of Web Functionality from an Untrusted Sourceweakness classshows
CWE-841Improper Enforcement of Behavioral Workflowweakness classshows
CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')weakness classshows
CWE-90Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')weakness classshows
CWE-915Improperly Controlled Modification of Dynamically-Determined Object Attributesweakness classshows
CWE-918Server-Side Request Forgery (SSRF)weakness classshows
CWE-922Insecure Storage of Sensitive Informationweakness classshows
CWE-94Improper Control of Generation of Code ('Code Injection')weakness classshows
CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')weakness classshows
CWE-98Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')weakness classshows

NIST SP 800-53r5 (546)

IDRequirementDomainClassification
AC-2Account ManagementAccess Controlsupports
AC-2.1Automated System Account ManagementAccess Controlsupports
AC-2.2Automated Temporary and Emergency Account ManagementAccess Controlsupports
AC-2.3Disable AccountsAccess Controlsupports
AC-2.4Automated Audit ActionsAccess Controlshows
AC-2.5Inactivity LogoutAccess Controlshows
AC-2.6Dynamic Privilege ManagementAccess Controlsupports
AC-2.7Privileged User AccountsAccess Controlsupports
AC-2.8Dynamic Account ManagementAccess Controlsupports
AC-2.9Restrictions on Use of Shared and Group AccountsAccess Controlsupports
AC-2.10Shared and Group Account Credential ChangeAccess Controlsupports
AC-2.11Usage ConditionsAccess Controlsupports
AC-2.12Account Monitoring for Atypical UsageAccess Controlshows
AC-2.13Disable Accounts for High-risk IndividualsAccess Controlsupports
AC-3Access EnforcementAccess Controlshows
AC-3.1Restricted Access to Privileged FunctionsAccess Controlsupports
AC-3.2Dual AuthorizationAccess Controlshows
AC-3.3Mandatory Access ControlAccess Controlsupports
AC-3.4Discretionary Access ControlAccess Controlsupports
AC-3.5Security-relevant InformationAccess Controlsupports
AC-3.6Protection of User and System InformationAccess Controlsupports
AC-3.7Role-based Access ControlAccess Controlsupports
AC-3.8Revocation of Access AuthorizationsAccess Controlshows
AC-3.9Controlled ReleaseAccess Controlsupports
AC-3.10Audited Override of Access Control MechanismsAccess Controlshows
AC-3.11Restrict Access to Specific Information TypesAccess Controlsupports
AC-3.12Assert and Enforce Application AccessAccess Controlsupports
AC-3.13Attribute-based Access ControlAccess Controlsupports
AC-3.14Individual AccessAccess Controlsupports
AC-3.15Discretionary and Mandatory Access ControlAccess Controlsupports
AC-4Information Flow EnforcementAccess Controlshows
AC-4.1Object Security and Privacy AttributesAccess Controlsupports
AC-4.2Processing DomainsAccess Controlsupports
AC-4.3Dynamic Information Flow ControlAccess Controlshows
AC-4.4Flow Control of Encrypted InformationAccess Controlsupports
AC-4.5Embedded Data TypesAccess Controlsupports
AC-4.6MetadataAccess Controlsupports
AC-4.7One-way Flow MechanismsAccess Controlsupports
AC-4.8Security and Privacy Policy FiltersAccess Controlsupports
AC-4.9Human ReviewsAccess Controlsupports
AC-4.10Enable and Disable Security or Privacy Policy FiltersAccess Controlsupports
AC-4.11Configuration of Security or Privacy Policy FiltersAccess Controlsupports
AC-4.12Data Type IdentifiersAccess Controlsupports
AC-4.13Decomposition into Policy-relevant SubcomponentsAccess Controlsupports
AC-4.14Security or Privacy Policy Filter ConstraintsAccess Controlsupports
AC-4.16Information Transfers on Interconnected SystemsAccess Controlsupports
AC-4.17Domain AuthenticationAccess Controlsupports
AC-4.18Security Attribute BindingAccess Controlsupports
AC-4.19Validation of MetadataAccess Controlsupports
AC-4.20Approved SolutionsAccess Controlsupports
AC-4.22Access OnlyAccess Controlsupports
AC-4.23Modify Non-releasable InformationAccess Controlsupports
AC-4.24Internal Normalized FormatAccess Controlsupports
AC-4.25Data SanitizationAccess Controlsupports
AC-4.26Audit Filtering ActionsAccess Controlshows
AC-4.27Redundant/Independent Filtering MechanismsAccess Controlsupports
AC-4.28Linear Filter PipelinesAccess Controlsupports
AC-4.29Filter Orchestration EnginesAccess Controlsupports
AC-4.30Filter Mechanisms Using Multiple ProcessesAccess Controlsupports
AC-4.31Failed Content Transfer PreventionAccess Controlshows
AC-4.32Process Requirements for Information TransferAccess Controlsupports
AC-5Separation of DutiesAccess Controlshows
AC-6Least PrivilegeAccess Controlshows
AC-6.1Authorize Access to Security FunctionsAccess Controlshows
AC-6.2Non-privileged Access for Nonsecurity FunctionsAccess Controlsupports
AC-6.3Network Access to Privileged CommandsAccess Controlsupports
AC-6.4Separate Processing DomainsAccess Controlsupports
AC-6.5Privileged AccountsAccess Controlsupports
AC-6.6Privileged Access by Non-organizational UsersAccess Controlsupports
AC-6.7Review of User PrivilegesAccess Controlsupports
AC-6.8Privilege Levels for Code ExecutionAccess Controlsupports
AC-6.9Log Use of Privileged FunctionsAccess Controlshows
AC-6.10Prohibit Non-privileged Users from Executing Privileged FunctionsAccess Controlsupports
AC-7Unsuccessful Logon AttemptsAccess Controlshows
AC-7.1Automatic Account LockAccess Controlsupports
AC-7.2Purge or Wipe Mobile DeviceAccess Controlsupports
AC-7.3Biometric Attempt LimitingAccess Controlsupports
AC-7.4Use of Alternate Authentication FactorAccess Controlsupports
AC-8System Use NotificationAccess Controlsupports
AC-9Previous Logon NotificationAccess Controlshows
AC-9.1Unsuccessful LogonsAccess Controlshows
AC-9.2Successful and Unsuccessful LogonsAccess Controlshows
AC-9.3Notification of Account ChangesAccess Controlsupports
AC-9.4Additional Logon InformationAccess Controlshows
AC-10Concurrent Session ControlAccess Controlshows
AC-11Device LockAccess Controlsupports
AC-11.1Pattern-hiding DisplaysAccess Controlsupports
AC-12Session TerminationAccess Controlshows
AC-12.1User-initiated LogoutsAccess Controlshows
AC-12.2Termination MessageAccess Controlsupports
AC-12.3Timeout Warning MessageAccess Controlsupports
AC-13Supervision and Review — Access ControlAccess Controlsupports
AC-14Permitted Actions Without Identification or AuthenticationAccess Controlsupports
AC-14.1Necessary UsesAccess Controlsupports
AC-15Automated MarkingAccess Controlsupports
AC-16Security and Privacy AttributesAccess Controlsupports
AC-16.1Dynamic Attribute AssociationAccess Controlsupports
AC-16.2Attribute Value Changes by Authorized IndividualsAccess Controlshows
AC-16.3Maintenance of Attribute Associations by SystemAccess Controlsupports
AC-16.4Association of Attributes by Authorized IndividualsAccess Controlshows
AC-16.5Attribute Displays on Objects to Be OutputAccess Controlsupports
AC-16.6Maintenance of Attribute AssociationAccess Controlsupports
AC-16.7Consistent Attribute InterpretationAccess Controlsupports
AC-16.8Association Techniques and TechnologiesAccess Controlshows
AC-16.9Attribute Reassignment — Regrading MechanismsAccess Controlsupports
AC-16.10Attribute Configuration by Authorized IndividualsAccess Controlshows
AC-17Remote AccessAccess Controlsupports
AC-17.1Monitoring and ControlAccess Controlshows
AC-17.2Protection of Confidentiality and Integrity Using EncryptionAccess Controlshows
AC-17.3Managed Access Control PointsAccess Controlsupports
AC-17.4Privileged Commands and AccessAccess Controlsupports
AC-17.5Monitoring for Unauthorized ConnectionsAccess Controlshows
AC-17.6Protection of Mechanism InformationAccess Controlsupports
AC-17.7Additional Protection for Security Function AccessAccess Controlsupports
AC-17.8Disable Nonsecure Network ProtocolsAccess Controlsupports
AC-17.9Disconnect or Disable AccessAccess Controlsupports
AC-17.10Authenticate Remote CommandsAccess Controlsupports
AC-18Wireless AccessAccess Controlsupports
AC-18.1Authentication and EncryptionAccess Controlsupports
AC-18.2Monitoring Unauthorized ConnectionsAccess Controlshows
AC-18.3Disable Wireless NetworkingAccess Controlsupports
AC-18.4Restrict Configurations by UsersAccess Controlsupports
AC-18.5Antennas and Transmission Power LevelsAccess Controlsupports
AC-19Access Control for Mobile DevicesAccess Controlsupports
AC-19.1Use of Writable and Portable Storage DevicesAccess Controlsupports
AC-19.2Use of Personally Owned Portable Storage DevicesAccess Controlsupports
AC-19.3Use of Portable Storage Devices with No Identifiable OwnerAccess Controlsupports
AC-19.4Restrictions for Classified InformationAccess Controlsupports
AC-19.5Full Device or Container-based EncryptionAccess Controlsupports
AC-20Use of External SystemsAccess Controlsupports
AC-20.1Limits on Authorized UseAccess Controlshows
AC-20.2Portable Storage Devices — Restricted UseAccess Controlsupports
AC-20.3Non-organizationally Owned Systems — Restricted UseAccess Controlsupports
AC-20.4Network Accessible Storage Devices — Prohibited UseAccess Controlsupports
AC-20.5Portable Storage Devices — Prohibited UseAccess Controlsupports
AC-21Information SharingAccess Controlsupports
AC-21.1Automated Decision SupportAccess Controlsupports
AC-21.2Information Search and RetrievalAccess Controlsupports
AC-22Publicly Accessible ContentAccess Controlsupports
AC-23Data Mining ProtectionAccess Controlsupports
AC-24Access Control DecisionsAccess Controlsupports
AC-24.1Transmit Access Authorization InformationAccess Controlshows
AC-24.2No User or Process IdentityAccess Controlsupports
AC-25Reference MonitorAccess Controlsupports
AU-2Event LoggingAudit and Accountabilityshows
AU-2.1Compilation of Audit Records from Multiple SourcesAudit and Accountabilityshows
AU-2.2Selection of Audit Events by ComponentAudit and Accountabilityshows
AU-2.3Reviews and UpdatesAudit and Accountabilitysupports
AU-2.4Privileged FunctionsAudit and Accountabilitysupports
AU-3Content of Audit RecordsAudit and Accountabilityshows
AU-3.1Additional Audit InformationAudit and Accountabilityshows
AU-3.2Centralized Management of Planned Audit Record ContentAudit and Accountabilityshows
AU-3.3Limit Personally Identifiable Information ElementsAudit and Accountabilitysupports
AU-4Audit Log Storage CapacityAudit and Accountabilityshows
AU-4.1Transfer to Alternate StorageAudit and Accountabilitysupports
AU-5Response to Audit Logging Process FailuresAudit and Accountabilityshows
AU-5.1Storage Capacity WarningAudit and Accountabilitysupports
AU-5.2Real-time AlertsAudit and Accountabilitysupports
AU-5.3Configurable Traffic Volume ThresholdsAudit and Accountabilitysupports
AU-5.4Shutdown on FailureAudit and Accountabilitysupports
AU-5.5Alternate Audit Logging CapabilityAudit and Accountabilityshows
AU-6Audit Record Review, Analysis, and ReportingAudit and Accountabilityshows
AU-6.1Automated Process IntegrationAudit and Accountabilitysupports
AU-6.2Automated Security AlertsAudit and Accountabilitysupports
AU-6.3Correlate Audit Record RepositoriesAudit and Accountabilityshows
AU-6.4Central Review and AnalysisAudit and Accountabilitysupports
AU-6.5Integrated Analysis of Audit RecordsAudit and Accountabilityshows
AU-6.7Permitted ActionsAudit and Accountabilitysupports
AU-6.8Full Text Analysis of Privileged CommandsAudit and Accountabilitysupports
AU-6.9Correlation with Information from Nontechnical SourcesAudit and Accountabilitysupports
AU-6.10Audit Level AdjustmentAudit and Accountabilityshows
AU-7Audit Record Reduction and Report GenerationAudit and Accountabilityshows
AU-7.1Automatic ProcessingAudit and Accountabilitysupports
AU-7.2Automatic Sort and SearchAudit and Accountabilitysupports
AU-8Time StampsAudit and Accountabilitysupports
AU-8.1Synchronization with Authoritative Time SourceAudit and Accountabilitysupports
AU-8.2Secondary Authoritative Time SourceAudit and Accountabilitysupports
AU-9Protection of Audit InformationAudit and Accountabilityshows
AU-9.1Hardware Write-once MediaAudit and Accountabilitysupports
AU-9.3Cryptographic ProtectionAudit and Accountabilitysupports
AU-9.4Access by Subset of Privileged UsersAudit and Accountabilitysupports
AU-9.5Dual AuthorizationAudit and Accountabilityshows
AU-9.6Read-only AccessAudit and Accountabilitysupports
AU-9.7Store on Component with Different Operating SystemAudit and Accountabilitysupports
AU-10Non-repudiationAudit and Accountabilitysupports
AU-10.1Association of IdentitiesAudit and Accountabilitysupports
AU-10.2Validate Binding of Information Producer IdentityAudit and Accountabilitysupports
AU-10.3Chain of CustodyAudit and Accountabilitysupports
AU-10.4Validate Binding of Information Reviewer IdentityAudit and Accountabilitysupports
AU-10.5Digital SignaturesAudit and Accountabilitysupports
AU-11Audit Record RetentionAudit and Accountabilityshows
AU-11.1Long-term Retrieval CapabilityAudit and Accountabilitysupports
AU-12Audit Record GenerationAudit and Accountabilityshows
AU-12.1System-wide and Time-correlated Audit TrailAudit and Accountabilityshows
AU-12.2Standardized FormatsAudit and Accountabilitysupports
AU-12.3Changes by Authorized IndividualsAudit and Accountabilityshows
AU-12.4Query Parameter Audits of Personally Identifiable InformationAudit and Accountabilityshows
AU-13Monitoring for Information DisclosureAudit and Accountabilityshows
AU-13.1Use of Automated ToolsAudit and Accountabilitysupports
AU-13.2Review of Monitored SitesAudit and Accountabilitysupports
AU-13.3Unauthorized Replication of InformationAudit and Accountabilityshows
AU-14Session AuditAudit and Accountabilityshows
AU-14.1System Start-upAudit and Accountabilitysupports
AU-14.2Capture and Record ContentAudit and Accountabilitysupports
AU-14.3Remote Viewing and ListeningAudit and Accountabilitysupports
AU-15Alternate Audit Logging CapabilityAudit and Accountabilityshows
AU-16Cross-organizational Audit LoggingAudit and Accountabilityshows
AU-16.1Identity PreservationAudit and Accountabilitysupports
AU-16.2Sharing of Audit InformationAudit and Accountabilityshows
AU-16.3DisassociabilityAudit and Accountabilitysupports
CM-2Baseline ConfigurationConfiguration Managementshows
CM-2.1Reviews and UpdatesConfiguration Managementsupports
CM-2.2Automation Support for Accuracy and CurrencyConfiguration Managementsupports
CM-2.3Retention of Previous ConfigurationsConfiguration Managementsupports
CM-2.4Unauthorized SoftwareConfiguration Managementshows
CM-2.5Authorized SoftwareConfiguration Managementshows
CM-2.6Development and Test EnvironmentsConfiguration Managementsupports
CM-2.7Configure Systems and Components for High-risk AreasConfiguration Managementsupports
CM-3Configuration Change ControlConfiguration Managementshows
CM-3.1Automated Documentation, Notification, and Prohibition of ChangesConfiguration Managementsupports
CM-3.2Testing, Validation, and Documentation of ChangesConfiguration Managementsupports
CM-3.3Automated Change ImplementationConfiguration Managementsupports
CM-3.4Security and Privacy RepresentativesConfiguration Managementsupports
CM-3.5Automated Security ResponseConfiguration Managementsupports
CM-3.6Cryptography ManagementConfiguration Managementsupports
CM-3.7Review System ChangesConfiguration Managementsupports
CM-3.8Prevent or Restrict Configuration ChangesConfiguration Managementshows
CM-4Impact AnalysesConfiguration Managementsupports
CM-4.1Separate Test EnvironmentsConfiguration Managementsupports
CM-4.2Verification of ControlsConfiguration Managementsupports
CM-5Access Restrictions for ChangeConfiguration Managementsupports
CM-5.1Automated Access Enforcement and Audit RecordsConfiguration Managementshows
CM-5.2Review System ChangesConfiguration Managementsupports
CM-5.3Signed ComponentsConfiguration Managementsupports
CM-5.4Dual AuthorizationConfiguration Managementshows
CM-5.5Privilege Limitation for Production and OperationConfiguration Managementsupports
CM-5.6Limit Library PrivilegesConfiguration Managementsupports
CM-5.7Automatic Implementation of Security SafeguardsConfiguration Managementsupports
CM-6Configuration SettingsConfiguration Managementsupports
CM-6.1Automated Management, Application, and VerificationConfiguration Managementsupports
CM-6.2Respond to Unauthorized ChangesConfiguration Managementshows
CM-6.3Unauthorized Change DetectionConfiguration Managementshows
CM-6.4Conformance DemonstrationConfiguration Managementsupports
CM-7Least FunctionalityConfiguration Managementsupports
CM-7.1Periodic ReviewConfiguration Managementsupports
CM-7.2Prevent Program ExecutionConfiguration Managementshows
CM-7.3Registration ComplianceConfiguration Managementsupports
CM-7.4Unauthorized Software — Deny-by-exceptionConfiguration Managementshows
CM-7.5Authorized Software — Allow-by-exceptionConfiguration Managementshows
CM-7.6Confined Environments with Limited PrivilegesConfiguration Managementsupports
CM-7.7Code Execution in Protected EnvironmentsConfiguration Managementsupports
CM-7.8Binary or Machine Executable CodeConfiguration Managementsupports
CM-7.9Prohibiting The Use of Unauthorized HardwareConfiguration Managementshows
CM-8System Component InventoryConfiguration Managementsupports
CM-8.1Updates During Installation and RemovalConfiguration Managementsupports
CM-8.2Automated MaintenanceConfiguration Managementsupports
CM-8.3Automated Unauthorized Component DetectionConfiguration Managementshows
CM-8.4Accountability InformationConfiguration Managementsupports
CM-8.5No Duplicate Accounting of ComponentsConfiguration Managementsupports
CM-8.6Assessed Configurations and Approved DeviationsConfiguration Managementsupports
CM-8.7Centralized RepositoryConfiguration Managementsupports
CM-8.8Automated Location TrackingConfiguration Managementsupports
CM-8.9Assignment of Components to SystemsConfiguration Managementsupports
CM-9.1Assignment of ResponsibilityConfiguration Managementsupports
CM-10Software Usage RestrictionsConfiguration Managementsupports
CM-10.1Open-source SoftwareConfiguration Managementsupports
CM-11User-installed SoftwareConfiguration Managementsupports
CM-11.1Alerts for Unauthorized InstallationsConfiguration Managementshows
CM-11.2Software Installation with Privileged StatusConfiguration Managementsupports
CM-11.3Automated Enforcement and MonitoringConfiguration Managementshows
CM-12Information LocationConfiguration Managementsupports
CM-12.1Automated Tools to Support Information LocationConfiguration Managementsupports
CM-13Data Action MappingConfiguration Managementsupports
CM-14Signed ComponentsConfiguration Managementsupports
SC-2Separation of System and User FunctionalitySystem and Communications Protectionsupports
SC-2.1Interfaces for Non-privileged UsersSystem and Communications Protectionsupports
SC-2.2DisassociabilitySystem and Communications Protectionsupports
SC-3Security Function IsolationSystem and Communications Protectionsupports
SC-3.1Hardware SeparationSystem and Communications Protectionsupports
SC-3.2Access and Flow Control FunctionsSystem and Communications Protectionsupports
SC-3.3Minimize Nonsecurity FunctionalitySystem and Communications Protectionsupports
SC-3.4Module Coupling and CohesivenessSystem and Communications Protectionsupports
SC-3.5Layered StructuresSystem and Communications Protectionsupports
SC-4Information in Shared System ResourcesSystem and Communications Protectionsupports
SC-4.1Security LevelsSystem and Communications Protectionsupports
SC-4.2Multilevel or Periods ProcessingSystem and Communications Protectionsupports
SC-5Denial-of-service ProtectionSystem and Communications Protectionsupports
SC-5.1Restrict Ability to Attack Other SystemsSystem and Communications Protectionsupports
SC-5.2Capacity, Bandwidth, and RedundancySystem and Communications Protectionsupports
SC-5.3Detection and MonitoringSystem and Communications Protectionshows
SC-6Resource AvailabilitySystem and Communications Protectionsupports
SC-7Boundary ProtectionSystem and Communications Protectionshows
SC-7.2Public AccessSystem and Communications Protectionsupports
SC-7.3Access PointsSystem and Communications Protectionsupports
SC-7.4External Telecommunications ServicesSystem and Communications Protectionsupports
SC-7.5Deny by Default — Allow by ExceptionSystem and Communications Protectionshows
SC-7.6Response to Recognized FailuresSystem and Communications Protectionsupports
SC-7.7Split Tunneling for Remote DevicesSystem and Communications Protectionsupports
SC-7.8Route Traffic to Authenticated Proxy ServersSystem and Communications Protectionsupports
SC-7.9Restrict Threatening Outgoing Communications TrafficSystem and Communications Protectionsupports
SC-7.10Prevent ExfiltrationSystem and Communications Protectionshows
SC-7.11Restrict Incoming Communications TrafficSystem and Communications Protectionsupports
SC-7.12Host-based ProtectionSystem and Communications Protectionsupports
SC-7.13Isolation of Security Tools, Mechanisms, and Support ComponentsSystem and Communications Protectionsupports
SC-7.15Networked Privileged AccessesSystem and Communications Protectionsupports
SC-7.16Prevent Discovery of System ComponentsSystem and Communications Protectionshows
SC-7.17Automated Enforcement of Protocol FormatsSystem and Communications Protectionsupports
SC-7.18Fail SecureSystem and Communications Protectionsupports
SC-7.19Block Communication from Non-organizationally Configured HostsSystem and Communications Protectionsupports
SC-7.20Dynamic Isolation and SegregationSystem and Communications Protectionsupports
SC-7.21Isolation of System ComponentsSystem and Communications Protectionsupports
SC-7.22Separate Subnets for Connecting to Different Security DomainsSystem and Communications Protectionsupports
SC-7.23Disable Sender Feedback on Protocol Validation FailureSystem and Communications Protectionsupports
SC-7.24Personally Identifiable InformationSystem and Communications Protectionsupports
SC-7.25Unclassified National Security System ConnectionsSystem and Communications Protectionsupports
SC-7.26Classified National Security System ConnectionsSystem and Communications Protectionsupports
SC-7.27Unclassified Non-national Security System ConnectionsSystem and Communications Protectionsupports
SC-7.28Connections to Public NetworksSystem and Communications Protectionsupports
SC-7.29Separate Subnets to Isolate FunctionsSystem and Communications Protectionsupports
SC-8Transmission Confidentiality and IntegritySystem and Communications Protectionshows
SC-8.1Cryptographic ProtectionSystem and Communications Protectionsupports
SC-8.2Pre- and Post-transmission HandlingSystem and Communications Protectionsupports
SC-8.3Cryptographic Protection for Message ExternalsSystem and Communications Protectionsupports
SC-8.4Conceal or Randomize CommunicationsSystem and Communications Protectionsupports
SC-8.5Protected Distribution SystemSystem and Communications Protectionsupports
SC-9Transmission ConfidentialitySystem and Communications Protectionsupports
SC-10Network DisconnectSystem and Communications Protectionsupports
SC-11Trusted PathSystem and Communications Protectionsupports
SC-11.1Irrefutable Communications PathSystem and Communications Protectionsupports
SC-12Cryptographic Key Establishment and ManagementSystem and Communications Protectionsupports
SC-12.1AvailabilitySystem and Communications Protectionsupports
SC-12.2Symmetric KeysSystem and Communications Protectionsupports
SC-12.3Asymmetric KeysSystem and Communications Protectionsupports
SC-12.4PKI CertificatesSystem and Communications Protectionsupports
SC-12.5PKI Certificates / Hardware TokensSystem and Communications Protectionsupports
SC-13Cryptographic ProtectionSystem and Communications Protectionsupports
SC-13.1FIPS-validated CryptographySystem and Communications Protectionsupports
SC-13.2NSA-approved CryptographySystem and Communications Protectionsupports
SC-13.3Individuals Without Formal Access ApprovalsSystem and Communications Protectionsupports
SC-13.4Digital SignaturesSystem and Communications Protectionsupports
SC-14Public Access ProtectionsSystem and Communications Protectionsupports
SC-15Collaborative Computing Devices and ApplicationsSystem and Communications Protectionsupports
SC-15.2Blocking Inbound and Outbound Communications TrafficSystem and Communications Protectionsupports
SC-15.3Disabling and Removal in Secure Work AreasSystem and Communications Protectionsupports
SC-15.4Explicitly Indicate Current ParticipantsSystem and Communications Protectionsupports
SC-16Transmission of Security and Privacy AttributesSystem and Communications Protectionsupports
SC-16.1Integrity VerificationSystem and Communications Protectionshows
SC-16.2Anti-spoofing MechanismsSystem and Communications Protectionsupports
SC-16.3Cryptographic BindingSystem and Communications Protectionsupports
SC-17Public Key Infrastructure CertificatesSystem and Communications Protectionsupports
SC-18Mobile CodeSystem and Communications Protectionsupports
SC-18.1Identify Unacceptable Code and Take Corrective ActionsSystem and Communications Protectionsupports
SC-18.2Acquisition, Development, and UseSystem and Communications Protectionsupports
SC-18.3Prevent Downloading and ExecutionSystem and Communications Protectionshows
SC-18.4Prevent Automatic ExecutionSystem and Communications Protectionshows
SC-18.5Allow Execution Only in Confined EnvironmentsSystem and Communications Protectionsupports
SC-19Voice Over Internet ProtocolSystem and Communications Protectionsupports
SC-20Secure Name/Address Resolution Service (Authoritative Source)System and Communications Protectionsupports
SC-20.1Child SubspacesSystem and Communications Protectionsupports
SC-20.2Data Origin and IntegritySystem and Communications Protectionshows
SC-21Secure Name/Address Resolution Service (Recursive or Caching Resolver)System and Communications Protectionsupports
SC-21.1Data Origin and IntegritySystem and Communications Protectionshows
SC-22Architecture and Provisioning for Name/Address Resolution ServiceSystem and Communications Protectionsupports
SC-23Session AuthenticitySystem and Communications Protectionshows
SC-23.1Invalidate Session Identifiers at LogoutSystem and Communications Protectionshows
SC-23.2User-initiated Logouts and Message DisplaysSystem and Communications Protectionshows
SC-23.3Unique System-generated Session IdentifiersSystem and Communications Protectionshows
SC-23.4Unique Session Identifiers with RandomizationSystem and Communications Protectionshows
SC-23.5Allowed Certificate AuthoritiesSystem and Communications Protectionsupports
SC-24Fail in Known StateSystem and Communications Protectionsupports
SC-25Thin NodesSystem and Communications Protectionsupports
SC-26DecoysSystem and Communications Protectionsupports
SC-26.1Detection of Malicious CodeSystem and Communications Protectionshows
SC-27Platform-independent ApplicationsSystem and Communications Protectionsupports
SC-28Protection of Information at RestSystem and Communications Protectionsupports
SC-28.1Cryptographic ProtectionSystem and Communications Protectionsupports
SC-28.2Offline StorageSystem and Communications Protectionsupports
SC-28.3Cryptographic KeysSystem and Communications Protectionsupports
SC-29HeterogeneitySystem and Communications Protectionsupports
SC-29.1Virtualization TechniquesSystem and Communications Protectionsupports
SC-30Concealment and MisdirectionSystem and Communications Protectionsupports
SC-30.1Virtualization TechniquesSystem and Communications Protectionsupports
SC-30.2RandomnessSystem and Communications Protectionsupports
SC-30.3Change Processing and Storage LocationsSystem and Communications Protectionsupports
SC-30.4Misleading InformationSystem and Communications Protectionsupports
SC-30.5Concealment of System ComponentsSystem and Communications Protectionsupports
SC-31Covert Channel AnalysisSystem and Communications Protectionsupports
SC-31.1Test Covert Channels for ExploitabilitySystem and Communications Protectionsupports
SC-31.2Maximum BandwidthSystem and Communications Protectionsupports
SC-31.3Measure Bandwidth in Operational EnvironmentsSystem and Communications Protectionsupports
SC-32System PartitioningSystem and Communications Protectionsupports
SC-33Transmission Preparation IntegritySystem and Communications Protectionshows
SC-34Non-modifiable Executable ProgramsSystem and Communications Protectionsupports
SC-34.1No Writable StorageSystem and Communications Protectionsupports
SC-34.2Integrity Protection on Read-only MediaSystem and Communications Protectionshows
SC-34.3Hardware-based ProtectionSystem and Communications Protectionsupports
SC-35External Malicious Code IdentificationSystem and Communications Protectionshows
SC-36Distributed Processing and StorageSystem and Communications Protectionsupports
SC-36.1Polling TechniquesSystem and Communications Protectionsupports
SC-36.2SynchronizationSystem and Communications Protectionsupports
SC-37Out-of-band ChannelsSystem and Communications Protectionsupports
SC-37.1Ensure Delivery and TransmissionSystem and Communications Protectionsupports
SC-38Operations SecuritySystem and Communications Protectionsupports
SC-39Process IsolationSystem and Communications Protectionsupports
SC-39.1Hardware SeparationSystem and Communications Protectionsupports
SC-39.2Separate Execution Domain Per ThreadSystem and Communications Protectionsupports
SC-40Wireless Link ProtectionSystem and Communications Protectionsupports
SC-40.1Electromagnetic InterferenceSystem and Communications Protectionsupports
SC-40.2Reduce Detection PotentialSystem and Communications Protectionsupports
SC-40.3Imitative or Manipulative Communications DeceptionSystem and Communications Protectionsupports
SC-40.4Signal Parameter IdentificationSystem and Communications Protectionsupports
SC-41Port and I/O Device AccessSystem and Communications Protectionsupports
SC-42Sensor Capability and DataSystem and Communications Protectionsupports
SC-42.1Reporting to Authorized Individuals or RolesSystem and Communications Protectionshows
SC-42.2Authorized UseSystem and Communications Protectionshows
SC-42.3Prohibit Use of DevicesSystem and Communications Protectionsupports
SC-42.4Notice of CollectionSystem and Communications Protectionsupports
SC-42.5Collection MinimizationSystem and Communications Protectionsupports
SC-43Usage RestrictionsSystem and Communications Protectionsupports
SC-44Detonation ChambersSystem and Communications Protectionsupports
SC-45System Time SynchronizationSystem and Communications Protectionsupports
SC-45.1Synchronization with Authoritative Time SourceSystem and Communications Protectionsupports
SC-45.2Secondary Authoritative Time SourceSystem and Communications Protectionsupports
SC-46Cross Domain Policy EnforcementSystem and Communications Protectionsupports
SC-47Alternate Communications PathsSystem and Communications Protectionsupports
SC-48Sensor RelocationSystem and Communications Protectionsupports
SC-48.1Dynamic Relocation of Sensors or Monitoring CapabilitiesSystem and Communications Protectionshows
SC-49Hardware-enforced Separation and Policy EnforcementSystem and Communications Protectionsupports
SC-50Software-enforced Separation and Policy EnforcementSystem and Communications Protectionsupports
SC-51Hardware-based ProtectionSystem and Communications Protectionsupports
SI-2Flaw RemediationSystem and Information Integrityshows
SI-2.1Central ManagementSystem and Information Integritysupports
SI-2.2Automated Flaw Remediation StatusSystem and Information Integrityshows
SI-2.3Time to Remediate Flaws and Benchmarks for Corrective ActionsSystem and Information Integritysupports
SI-2.4Automated Patch Management ToolsSystem and Information Integritysupports
SI-2.5Automatic Software and Firmware UpdatesSystem and Information Integritysupports
SI-2.6Removal of Previous Versions of Software and FirmwareSystem and Information Integritysupports
SI-2.7Root Cause AnalysisSystem and Information Integritysupports
SI-3Malicious Code ProtectionSystem and Information Integrityshows
SI-3.1Central ManagementSystem and Information Integritysupports
SI-3.2Automatic UpdatesSystem and Information Integritysupports
SI-3.3Non-privileged UsersSystem and Information Integritysupports
SI-3.4Updates Only by Privileged UsersSystem and Information Integritysupports
SI-3.5Portable Storage DevicesSystem and Information Integritysupports
SI-3.6Testing and VerificationSystem and Information Integritysupports
SI-3.7Nonsignature-based DetectionSystem and Information Integritysupports
SI-3.8Detect Unauthorized CommandsSystem and Information Integrityshows
SI-3.9Authenticate Remote CommandsSystem and Information Integritysupports
SI-3.10Malicious Code AnalysisSystem and Information Integrityshows
SI-4System MonitoringSystem and Information Integrityshows
SI-4.1System-wide Intrusion Detection SystemSystem and Information Integritysupports
SI-4.2Automated Tools and Mechanisms for Real-time AnalysisSystem and Information Integritysupports
SI-4.3Automated Tool and Mechanism IntegrationSystem and Information Integritysupports
SI-4.4Inbound and Outbound Communications TrafficSystem and Information Integritysupports
SI-4.5System-generated AlertsSystem and Information Integritysupports
SI-4.6Restrict Non-privileged UsersSystem and Information Integritysupports
SI-4.7Automated Response to Suspicious EventsSystem and Information Integrityshows
SI-4.8Protection of Monitoring InformationSystem and Information Integrityshows
SI-4.9Testing of Monitoring Tools and MechanismsSystem and Information Integrityshows
SI-4.10Visibility of Encrypted CommunicationsSystem and Information Integritysupports
SI-4.11Analyze Communications Traffic AnomaliesSystem and Information Integritysupports
SI-4.12Automated Organization-generated AlertsSystem and Information Integritysupports
SI-4.13Analyze Traffic and Event PatternsSystem and Information Integrityshows
SI-4.14Wireless Intrusion DetectionSystem and Information Integritysupports
SI-4.15Wireless to Wireline CommunicationsSystem and Information Integritysupports
SI-4.16Correlate Monitoring InformationSystem and Information Integrityshows
SI-4.18Analyze Traffic and Covert ExfiltrationSystem and Information Integritysupports
SI-4.19Risk for IndividualsSystem and Information Integritysupports
SI-4.20Privileged UsersSystem and Information Integritysupports
SI-4.21Probationary PeriodsSystem and Information Integritysupports
SI-4.22Unauthorized Network ServicesSystem and Information Integrityshows
SI-4.23Host-based DevicesSystem and Information Integritysupports
SI-4.24Indicators of CompromiseSystem and Information Integritysupports
SI-4.25Optimize Network Traffic AnalysisSystem and Information Integritysupports
SI-5Security Alerts, Advisories, and DirectivesSystem and Information Integritysupports
SI-5.1Automated Alerts and AdvisoriesSystem and Information Integritysupports
SI-6Security and Privacy Function VerificationSystem and Information Integritysupports
SI-6.1Notification of Failed Security TestsSystem and Information Integritysupports
SI-6.2Automation Support for Distributed TestingSystem and Information Integritysupports
SI-6.3Report Verification ResultsSystem and Information Integritysupports
SI-7Software, Firmware, and Information IntegritySystem and Information Integrityshows
SI-7.1Integrity ChecksSystem and Information Integrityshows
SI-7.2Automated Notifications of Integrity ViolationsSystem and Information Integrityshows
SI-7.3Centrally Managed Integrity ToolsSystem and Information Integrityshows
SI-7.4Tamper-evident PackagingSystem and Information Integritysupports
SI-7.5Automated Response to Integrity ViolationsSystem and Information Integrityshows
SI-7.6Cryptographic ProtectionSystem and Information Integritysupports
SI-7.7Integration of Detection and ResponseSystem and Information Integritysupports
SI-7.8Auditing Capability for Significant EventsSystem and Information Integrityshows
SI-7.9Verify Boot ProcessSystem and Information Integritysupports
SI-7.10Protection of Boot FirmwareSystem and Information Integritysupports
SI-7.11Confined Environments with Limited PrivilegesSystem and Information Integritysupports
SI-7.12Integrity VerificationSystem and Information Integrityshows
SI-7.13Code Execution in Protected EnvironmentsSystem and Information Integritysupports
SI-7.14Binary or Machine Executable CodeSystem and Information Integritysupports
SI-7.15Code AuthenticationSystem and Information Integritysupports
SI-7.16Time Limit on Process Execution Without SupervisionSystem and Information Integritysupports
SI-7.17Runtime Application Self-protectionSystem and Information Integritysupports
SI-8Spam ProtectionSystem and Information Integritysupports
SI-8.1Central ManagementSystem and Information Integritysupports
SI-8.2Automatic UpdatesSystem and Information Integritysupports
SI-8.3Continuous Learning CapabilitySystem and Information Integritysupports
SI-9Information Input RestrictionsSystem and Information Integritysupports
SI-10Information Input ValidationSystem and Information Integrityshows
SI-10.1Manual Override CapabilitySystem and Information Integritysupports
SI-10.2Review and Resolve ErrorsSystem and Information Integrityshows
SI-10.3Predictable BehaviorSystem and Information Integritysupports
SI-10.4Timing InteractionsSystem and Information Integritysupports
SI-10.5Restrict Inputs to Trusted Sources and Approved FormatsSystem and Information Integritysupports
SI-10.6Injection PreventionSystem and Information Integrityshows
SI-11Error HandlingSystem and Information Integrityshows
SI-12Information Management and RetentionSystem and Information Integritysupports
SI-12.1Limit Personally Identifiable Information ElementsSystem and Information Integritysupports
SI-12.3Information DisposalSystem and Information Integritysupports
SI-13Predictable Failure PreventionSystem and Information Integrityshows
SI-13.1Transferring Component ResponsibilitiesSystem and Information Integritysupports
SI-13.2Time Limit on Process Execution Without SupervisionSystem and Information Integritysupports
SI-13.3Manual Transfer Between ComponentsSystem and Information Integritysupports
SI-13.4Standby Component Installation and NotificationSystem and Information Integritysupports
SI-13.5Failover CapabilitySystem and Information Integritysupports
SI-14Non-persistenceSystem and Information Integritysupports
SI-14.1Refresh from Trusted SourcesSystem and Information Integritysupports
SI-14.2Non-persistent InformationSystem and Information Integritysupports
SI-14.3Non-persistent ConnectivitySystem and Information Integritysupports
SI-15Information Output FilteringSystem and Information Integritysupports
SI-16Memory ProtectionSystem and Information Integritysupports
SI-17Fail-safe ProceduresSystem and Information Integritysupports
SI-18Personally Identifiable Information Quality OperationsSystem and Information Integritysupports
SI-18.1Automation SupportSystem and Information Integritysupports
SI-18.2Data TagsSystem and Information Integritysupports
SI-18.3CollectionSystem and Information Integritysupports
SI-18.4Individual RequestsSystem and Information Integritysupports
SI-18.5Notice of Correction or DeletionSystem and Information Integritysupports
SI-19De-identificationSystem and Information Integritysupports
SI-19.1CollectionSystem and Information Integritysupports
SI-19.2ArchivingSystem and Information Integritysupports
SI-19.3ReleaseSystem and Information Integritysupports
SI-19.4Removal, Masking, Encryption, Hashing, or Replacement of Direct IdentifiersSystem and Information Integritysupports
SI-19.5Statistical Disclosure ControlSystem and Information Integritysupports
SI-19.6Differential PrivacySystem and Information Integritysupports
SI-19.7Validated Algorithms and SoftwareSystem and Information Integritysupports
SI-19.8Motivated IntruderSystem and Information Integritysupports
SI-20TaintingSystem and Information Integritysupports
SI-21Information RefreshSystem and Information Integritysupports
SI-22Information DiversitySystem and Information Integritysupports
SI-23Information FragmentationSystem and Information Integritysupports

ASVS content © OWASP Foundation, CC BY-SA 4.0. CWE is a trademark of The MITRE Corporation; CWE content used per MITRE's terms. NIST SP 800-53 is a work of the U.S. Government, public domain. Sources retrieved from the publishers' official repositories.

Back to the runtime behavior analysis