Frameworks registry
Open frameworks only. Nothing behind a paywall.
The public frameworks and taxonomies controls point to: government guides, MITRE, CWE, CVE. Frameworks under a restrictive license are not listed. Find which CIRSEC control covers a NIST, CISA or ANSSI item below.
01
Frameworks
| Key | Framework | Kind | References |
|---|---|---|---|
nist-800-53r5 | NIST SP 800-53 Rev. 5NIST | control-framework | none yet |
cisa-scuba-m365 | CISA SCuBA Microsoft 365 Secure Configuration BaselinesCISA | control-framework | none yet |
anssi-linux | ANSSI - Recommandations de sécurité relatives à un système GNU/LinuxANSSI | control-framework | none yet |
mitre-attack | MITRE ATT&CKMITRE | threat-taxonomy | none yet |
cwe | Common Weakness EnumerationMITRE | weakness-taxonomy | none yet |
cve | Common Vulnerabilities and ExposuresCVE Program | vulnerability-database | none yet |
control-framework entries are used in mappings, the other kinds in threats. Rendered from
baselines.yml on every deploy.
02
Cross-reference
No control references a framework yet.
03
Engines
| Key | Engine | Checks and scripts |
|---|---|---|
graph-api | Microsoft Graph APIGET a Graph resource and compare a JSON path to an expected value. | 0 |
exchange-powershell | Exchange Online PowerShellRun an Exchange Online PowerShell cmdlet and compare a property to an expected value. | 0 |
powershell | PowerShellGeneric PowerShell script, for checks or remediation. | 0 |
shell | POSIX shellShell command or script. For checks, exit code 0 means compliant. | 0 |
osquery | osqueryosquery SQL query. For checks, a non-empty result means compliant unless the spec says otherwise. | 0 |
windows-registry | Windows registryRead a registry value and compare it to an expected value. | 0 |
file-content | File contentMatch a regex against a configuration file. | 0 |
Each engine defines the spec payload of its checks. Adding one is a change to
baselines.yml, not to the schemas.