AC-12 Session Terminationac-12
Whether an AWS call fetches evidence for this control, and what to run. Its Rev5 baselines, the indicators that reach it and the FedRAMP guidance attached to it open below.
Nothing names itNo recipe names AC-12. 13 reach an indicator it shares, which is adjacency and not coverage — worth reading, not worth recording as evidence for this control.
Collect evidence (0)
Authored AWS recipes whose output is evidence for AC-12. This mapping is this project’s opinion (overlay v3.0.0), versioned separately from the dataset — the upstream FedRAMP rules name none of these tools.
No authored recipe names AC-12. The nearest authored work is below.
Nobody has assessed AC-12 against AWS and pipeline yet. That is a gap in this project’s research — not a finding about the control, and not a claim that nothing collects it.
The KSIs that reach it are KSI-CNA-ULN, KSI-IAM-ELP — that is where the authoring would land. Browse /collect for the whole authored corpus.
Reaches the same indicator, not AC-12
These recipes prove a KSI that reaches it. None of them claims AC-12 — treat them as neighbours worth reading, not as coverage.
- AWS Config compliance results proving the network boundary is controlled — no security group exposes SSH to the internet, groups open to 0.0.0.0/0 only allow authorized ports, and every VPC's default security group denies all traffic via KSI-CNA-ULN
- How operators actually reach the environment from outside it: the managed access paths that exist, the logging and encryption configured on them, the session-by-session record of who used them, and the negative check that no instance is directly reachable instead via KSI-CNA-ULN KSI-IAM-ELP
- The machine-generated inventory of every plane on which one part of the system reaches another — VPC peering connections, Transit Gateway attachments, the interface and gateway endpoints this account consumes, the endpoint connections other accounts have made INTO your endpoint service, and the security-group rules that name another group rather than a CIDR — each narrowed to the states that are actually live via KSI-CNA-ULN
- Account-wide credential report proving MFA is active per principal and that passwords/access keys are rotated within policy via KSI-IAM-ELP
- Full snapshot of every IAM user, group, role, and attached/inline policy with their relationships, used to review that granted permissions match least-privilege intent via KSI-IAM-ELP
What NIST requires of AC-12
The control statement from NIST 800-53 Rev5, verbatim. Square brackets are organization-defined parameters — yours to set, not FedRAMP's to dictate.
Automatically terminate a user session after [conditions or trigger events].
NIST SP 800-53 Rev5 catalog 5.2.0, from usnistgov/oscal-content at 78650f0. The FedRAMP dataset carries no control text; this is borrowed and pinned.
Rev5 baseline membership
Membership is the whole relationship — a baseline is a set of control ids. Class A carries no baseline at all. The Low/Moderate/High labels are an interpretation from control counts, not a dataset fact.
KSI indicators reaching this control (2)
Under 20x, these indicators are how this control is demonstrated — automated KSI evidence stands in for narrative control evidence.
- CNAKSI-CNA-ULNUsing Logical Networking
Logical networking and related capabilities are used and persistently reviewed to enforce traffic flow controls.
- IAMKSI-IAM-ELPEnsuring Least Privilege
Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.
Pages exist for the 209 controls reached by at least one KSI. Baseline-only controls are the orphans on /coverage. Control titles and full text live in the NIST catalog, not this dataset.