{
 "ok": true,
 "components": [
  {
   "component": "authentication",
   "asked_as": null,
   "concerns": [
    "session timeout",
    "access review"
   ],
   "matched_on": [
    "session timeout: session termination, session lock, device lock, inactivity logout, period of inactivity, automatic logoff, logout",
    "access review: account management, access review, activity review, recertif, access authorization, account monitoring"
   ],
   "provisions_matched": 63,
   "provisions_returned": 5,
   "provisions": [
    {
     "citation": "AC-12",
     "framework": "NIST SP 800-53 Rev 5.2.0",
     "control_id": "AC-12",
     "control_title": "Session Termination",
     "requirement": "Automatically terminate a user session after {{ insert: param, ac-12_odp }}.",
     "record_url": "https://referencesource.org/security-compliance-controls/ac-12/",
     "source_url": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json",
     "source_quote": "Automatically terminate a user session after {{ insert: param, ac-12_odp }}.",
     "requirement_resolved": "Automatically terminate a user session after [Assignment: organization-defined conditions or trigger events].",
     "requirement_resolved_note": "The same provision as requirement, with each of the publisher's {{ insert: param, ... }} markers replaced by what the catalogue says that parameter is. Words in square brackets are a value your organisation decides, not something NIST asserts. requirement above is the untouched verbatim text.",
     "family": "Access Control",
     "organization_defined": "conditions or trigger events",
     "publisher": "National Institute of Standards and Technology",
     "publisher_page": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",
     "matched_phrase": "session termination",
     "matched_in": "control_title",
     "concern": "session timeout",
     "names_the_concern": true,
     "cite": "NIST SP 800-53 Rev 5.2.0 AC-12 — Session Termination https://referencesource.org/security-compliance-controls/ac-12/"
    },
    {
     "citation": "AC-2a",
     "framework": "NIST SP 800-53 Rev 5.2.0",
     "control_id": "AC-2",
     "control_title": "Account Management",
     "requirement": "Define and document the types of accounts allowed and specifically prohibited for use within the system;",
     "record_url": "https://referencesource.org/security-compliance-controls/ac-2a/",
     "source_url": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json",
     "source_quote": "Define and document the types of accounts allowed and specifically prohibited for use within the system;",
     "family": "Access Control",
     "element": "a.",
     "publisher": "National Institute of Standards and Technology",
     "publisher_page": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",
     "matched_phrase": "account management",
     "matched_in": "control_title",
     "concern": "access review",
     "names_the_concern": true,
     "cite": "NIST SP 800-53 Rev 5.2.0 AC-2a — Account Management https://referencesource.org/security-compliance-controls/ac-2a/"
    },
    {
     "citation": "164.312(a)(2)(iii)",
     "framework": "HIPAA Security Rule (45 CFR part 164, subpart C)",
     "control_id": "164.312",
     "control_title": "Technical safeguards",
     "requirement": "(iii) Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity.",
     "record_url": "https://referencesource.org/security-compliance-controls/164-312-a-2-iii/",
     "source_url": "https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.312",
     "source_quote": "(iii) Automatic logoff (Addressable). Implement electronic procedures that terminate an electronic session after a predetermined time of inactivity.",
     "element": "(iii)",
     "publisher": "Office of the Federal Register (Code of Federal Regulations)",
     "publisher_page": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C",
     "matched_phrase": "automatic logoff",
     "matched_in": "requirement",
     "concern": "session timeout",
     "names_the_concern": true,
     "cite": "HIPAA Security Rule (45 CFR part 164, subpart C) 164.312(a)(2)(iii) — Technical safeguards https://referencesource.org/security-compliance-controls/164-312-a-2-iii/"
    },
    {
     "citation": "164.308(a)(1)(ii)(D)",
     "framework": "HIPAA Security Rule (45 CFR part 164, subpart C)",
     "control_id": "164.308",
     "control_title": "Administrative safeguards",
     "requirement": "(D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.",
     "record_url": "https://referencesource.org/security-compliance-controls/164-308-a-1-ii-d/",
     "source_url": "https://www.ecfr.gov/api/versioner/v1/full/2026-11-01/title-45.xml?part=164&section=164.308",
     "source_quote": "(D) Information system activity review (Required). Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports.",
     "element": "(D)",
     "publisher": "Office of the Federal Register (Code of Federal Regulations)",
     "publisher_page": "https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-C",
     "matched_phrase": "activity review",
     "matched_in": "requirement",
     "concern": "access review",
     "names_the_concern": true,
     "cite": "HIPAA Security Rule (45 CFR part 164, subpart C) 164.308(a)(1)(ii)(D) — Administrative safeguards https://referencesource.org/security-compliance-controls/164-308-a-1-ii-d/"
    },
    {
     "citation": "SC-23(1)",
     "framework": "NIST SP 800-53 Rev 5.2.0",
     "control_id": "SC-23(1)",
     "control_title": "Invalidate Session Identifiers at Logout",
     "requirement": "Invalidate session identifiers upon user logout or other session termination.",
     "record_url": "https://referencesource.org/security-compliance-controls/sc-23-1/",
     "source_url": "https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json",
     "source_quote": "Invalidate session identifiers upon user logout or other session termination.",
     "family": "System and Communications Protection",
     "publisher": "National Institute of Standards and Technology",
     "publisher_page": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",
     "matched_phrase": "logout",
     "matched_in": "control_title",
     "concern": "session timeout",
     "names_the_concern": true,
     "cite": "NIST SP 800-53 Rev 5.2.0 SC-23(1) — Invalidate Session Identifiers at Logout https://referencesource.org/security-compliance-controls/sc-23-1/"
    }
   ]
  }
 ],
 "regime": null,
 "regime_name": null,
 "ordering": "Each document in turn, the one with more matches on this concern leading, so the smaller document is never crowded out; inside a document, by how directly the provision's own words name the concern — first the ones whose own published name carries one of the matched phrases, then by how direct that phrase is, with a base provision before its enhancement, and last the ones whose own text narrows them to another subject (mobile devices, physical entry to a building, an off-site storage location). Ties keep catalogue order, so the same call always answers the same way.",
 "how_the_order_was_decided": "`provisions_matched` is every provision in these records whose published text carries one of the phrases in `matched_on`; `provisions_returned` is how many of them are printed. Which ones are printed is OURS and is decided only by how directly each provision's own words name the concern: Each document in turn, the one with more matches on this concern leading, so the smaller document is never crowded out; inside a document, by how directly the provision's own words name the concern — first the ones whose own published name carries one of the matched phrases, then by how direct that phrase is, with a base provision before its enhancement, and last the ones whose own text narrows them to another subject (mobile devices, physical entry to a building, an off-site storage location). Ties keep catalogue order, so the same call always answers the same way. A provision narrowed to another subject is ranked down, never dropped: it says so in `narrower_subject` when it is printed, it is still counted in `provisions_matched`, and the MCP tool controls_for on that concern lists it in this same order. Ask with the component the subject belongs to and it is no longer narrower — `component=laptop` ranks the mobile-device controls up, not down. To read the documents whole, https://referencesource.org/security-compliance-controls/data.json.",
 "subjects_that_rank_a_provision_down": [
  "mobile devices",
  "wireless networks",
  "remote access into the network",
  "voice over IP",
  "conferencing and collaboration devices",
  "portable storage media",
  "remote maintenance and diagnostics",
  "physical entry to a building",
  "a building or facility",
  "teleworking",
  "a fallback processing site",
  "an off-site storage location",
  "somebody else's system"
 ],
 "how_components_are_mapped": "The component vocabulary is OURS, not the publisher's: no document says which provisions govern 'a database'. Each component word is mapped to the concerns named in `concerns`, and each concern is matched by the literal phrases in `matched_on` appearing in the published title or text. If you disagree with a mapping, ask for the concerns directly with the MCP tool controls_for, or read the whole document at https://referencesource.org/security-compliance-controls/.",
 "records_searched": 2022,
 "scope": "This is the publisher's own text, verbatim. It states what must be true, not how to build it: decide the implementation yourself and cite the citation above in the code. Nothing here is legal advice, and a control being listed says nothing about whether it applies to your system.",
 "not_held": "SOC 2 (AICPA), ISO/IEC 27001 and PCI DSS are deliberately not in this dataset: that text is copyrighted by the bodies that sell it, so it cannot be republished here.",
 "attestation": "Each provision below is the publisher's own text out of our records, with the sentence we read it from and a link to it. A provision being listed says that its document contains it, NOT that it applies to your system and not how to satisfy it. Nothing here is legal advice.",
 "dataset": {
  "slug": "security-compliance-controls",
  "name": "Security and compliance controls, one provision at a time: NIST SP 800-53 and the HIPAA Security Rule in their own words",
  "url": "https://referencesource.org/security-compliance-controls/",
  "licence": "Both sources are US government works in the public domain: NIST SP 800-53 is published by NIST with its OSCAL rendering in a public GitHub repository, and the Code of Federal Regulations is published by the Office of the Federal Register. Each record links back to the exact API URL it was cut from and names the publisher's own page for the document. No text from SOC 2, ISO/IEC 27001 or PCI DSS appears anywhere in this dataset, because that text is copyrighted.",
  "last_verified": "2026-11-15",
  "stale_after": "2026-12-15"
 },
 "coverage": "complete",
 "recheck": "Every citation here can be re-checked later at https://referencesource.org/api/check?dataset=security-compliance-controls&id=<record id>&claim=<the text you stored>.",
 "answered_by": "referencesource.org /api/requirements (automated service)"
}
