United States

NIST SP 800-190

45 controls. 233 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

45 controls 233 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

NIST SP 800-190 Application Container Security Evidence & Implementation Kit

45 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
NIST190-01Shared responsibility model definition120
NIST190-02Cloud security policy and strategy10
NIST190-03Cloud risk assessment95
NIST190-04Regulatory compliance for cloud services35
NIST190-05Cloud security roles and responsibilities10
NIST190-06Cloud identity management24
NIST190-07Multi-factor authentication for cloud56
NIST190-08Privileged access in cloud environments50
NIST190-09Federation and single sign-on0
NIST190-10API security and access tokens0
NIST190-11Data classification for cloud89
NIST190-12Encryption of cloud-stored data109
NIST190-13Data residency and sovereignty0
NIST190-14Data backup and recovery in cloud53
NIST190-15Secure data deletion in cloud64
NIST190-16Virtual network segmentation41
NIST190-17Container and serverless security0
NIST190-18Cloud workload protection0
NIST190-19Image and template hardening37
NIST190-20Cloud configuration management37
NIST190-21Cloud security monitoring and logging65
NIST190-22Incident response in cloud84
NIST190-23Cloud vulnerability management40
NIST190-24Cloud change management29
NIST190-25Service level agreement management0
SP800-190-3.1Container Image Vulnerability Management0
SP800-190-3.10Network Segmentation Between Pods0
SP800-190-3.11Mixed Sensitivity Workload Isolation0
SP800-190-3.12Container Runtime Hardening0
SP800-190-3.13Host Operating System Minimization0
SP800-190-3.14Host Patch Management0
SP800-190-3.15Container File System Integrity0
SP800-190-3.16Container Logging and Visibility0
SP800-190-3.17Runtime Threat Detection0
SP800-190-3.18Incident Response for Containers0
SP800-190-3.19Supply Chain Risk for Third Party Images0
SP800-190-3.2Image Configuration Hardening0
SP800-190-3.20Secrets Management at Runtime0
SP800-190-3.3Embedded Secrets in Images0
SP800-190-3.4Image Trust and Provenance0
SP800-190-3.5Registry Authentication and Authorization0
SP800-190-3.6Registry Image Freshness0
SP800-190-3.7Orchestrator Authentication0
SP800-190-3.8Orchestrator Authorization with RBAC0
SP800-190-3.9Pod Security Standards0

Tell me when NIST SP 800-190 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • IAM policy
  • MFA enforcement report
  • Federation configuration
  • API token inventory
  • Kerberos/OAuth/FIDO2 configuration
  • session token settings
  • scan tool configuration
  • sample selection rationale
  • scan report with CVSS scores
  • remediation evidence

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for NIST SP 800-190, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition