Home/Compliance
nist-800-53

NIST 800-53. Security Controls

14 controls · cross-mapped to ATT&CK techniques
Translate between regulatory language and what attackers actually do. Each control maps to MITRE ATT&CK techniques; open a control to see those techniques and whether we hold detection coverage for them.
1246
Total controls
0%
Detection coverage
0
Covered controls
1246
Coverage gaps
▤ Export audit (CSV) Coverage report Self-assessment Show gaps only
▶ Check your own detection coverage

Paste the ATT&CK technique IDs you have Sigma/YARA rules for (one per line, e.g. T1059, T1190). The controls below will update to show YOUR coverage instead of ours.

Red team insight A nist-800-53 compliant org should have detection for the green-tagged techniques below. Controls showing no technique coverage are likely blind spots. Use gaps view to enumerate unmonitored attack paths.

Controls

14 shown of 14
Require the developer of the system, system component, or system service to follow a documented development process that: Explicitly addresses security and privacy requirements; Identifies the standards and tools used in the development process; Documents the specific tool options and tool configurations used in the development process; and Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and Review the development process, standards, tools, tool options, and tool configurations {{ insert: param, sa-15_odp.01 }} to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: {{ insert: param, sa-15_prm_2 }}.
family SA framework nist-800-53
Equivalent controls in other frameworks  click any to see its ATT&CK technique mappings
Require the developer of the system, system component, or system service to: Define quality metrics at the beginning of the development process; and Provide evidence of meeting the quality metrics {{ insert: param, sa-15.01_odp.01 }}.
family SA framework nist-800-53
Require the developer of the system, system component, or system service to provide, implement, and test an incident response plan.
family SA framework nist-800-53
Require the developer of the system or system component to archive the system or component to be released or delivered together with the corresponding evidence supporting the final security and privacy review.
family SA framework nist-800-53
Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.
family SA framework nist-800-53
Require the developer of the system or system component to minimize the use of personally identifiable information in development and test environments.
family SA framework nist-800-53
Require the developer of the system, system component, or system service to select and employ security and privacy tracking tools for use during the development process.
family SA framework nist-800-53
Require the developer of the system, system component, or system service to perform a criticality analysis: At the following decision points in the system development life cycle: {{ insert: param, sa-15.03_odp.01 }} ; and At the following level of rigor: {{ insert: param, sa-15.3_prm_2 }}.
family SA framework nist-800-53
family SA framework nist-800-53
Require the developer of the system, system component, or system service to reduce attack surfaces to {{ insert: param, sa-15.05_odp }}.
family SA framework nist-800-53
Require the developer of the system, system component, or system service to implement an explicit process to continuously improve the development process.
family SA framework nist-800-53
Require the developer of the system, system component, or system service {{ insert: param, sa-15.07_odp.01 }} to: Perform an automated vulnerability analysis using {{ insert: param, sa-15.07_odp.02 }}; Determine the exploitation potential for discovered vulnerabilities; Determine potential risk mitigations for delivered vulnerabilities; and Deliver the outputs of the tools and results of the analysis to {{ insert: param, sa-15.07_odp.03 }}.
family SA framework nist-800-53
Require the developer of the system, system component, or system service to use threat modeling and vulnerability analyses from similar systems, components, or services to inform the current development process.
family SA framework nist-800-53
family SA framework nist-800-53
Showing 1-14 of 14
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin