← all corpora

nist-sp800-sec

backlog row · status candidate · domain SEC (Security and vulnerabilities) · lane B · refresh pinned · tags US · IDENTITY · SECURITY

What an agent uses it for

an agent designing a control or wipe procedure queries this for what SP 800-53/61/63/88/207 actually require, clause-level

Use it
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/nist-sp800-sec.json
xerj corpus add --from ./nist-sp800-sec.json
xerj corpus index nist-sp800-sec then xerj code nist-sp800-sec "your question"

Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "nist-sp800-sec", once the corpus is indexed on the node.

Sources and pins

sourcepinlicencesizereview note
https://github.com/usnistgov/800-63-3 recipe?curated pack INTAKE RE-SCOPED 2026-10-04 from source survey (planned csrc.nist.gov/pubs/sp/800 is 404; CSRC has no bulk API and per-pub downloads are PDF-only: the famous prose pubs are unfetchable as text). Build instead from GitHub text sources: usnistgov/800-63-3 (SP 800-63-3 + vols A/B/C + FAQ as per-section Jekyll markdown: licence 'NIST Technical Series Publications': USG work, worldwide perpetual royalt
https://github.com/usnistgov/oscal-content recipe?curated pack see 800-63-3 entry

0 B across 0 files. Added n/a.

People behind this corpus

Upstream authors (1)

Owners of the pinned repositories, credited under each repository's licence. They have not signed up here; their pages are attribution.

usnistgov@usnistgov · upstream

All contributors.

Rights

?. See per-source review blocks. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.

Retrieval spot-check (G7)

1.0/5 relevant. Graded .

Q: How short can a password be if we let the user pick it themselves?
expect:
top-5: corpus-nist-sp800/sp800-63/sp800-63-3/sec4_model.md / corpus-nist-sp800/sp800-63/faq/63B/restricted.md / corpus-nist-sp800/sp800-63/faq/63C/authorizationcomponent.md / corpus-nist-sp800/sp800-63/faq/63B/commonpasswords.md / corpus-nist-sp800/sp800-63/sp800-63c/sec7_presentation.md
grade: miss
Q: Can we let people recover their account by answering security questions?
expect:
top-5: corpus-nist-sp800/sp800-63/faq/general/separation.md / corpus-nist-sp800/sp800-63/faq/general/federal.md / corpus-nist-sp800/sp800-63/faq/63B/kbareset.md / corpus-nist-sp800/sp800-63/faq/general/levels.md / corpus-nist-sp800/sp800-63/faq/63B/passwordmanagers.md
grade: pass
Q: Do we have to change the passwords vendors ship on new equipment before we start using it?
expect:
top-5: corpus-nist-sp800/sp800-63/faq/general/federal.md / corpus-nist-sp800/sp800-63/faq/63B/restricted.md / corpus-nist-sp800/sp800-63/faq/general/levels.md / corpus-nist-sp800/sp800-63/faq/63C/authorizationcomponent.md / corpus-nist-sp800/sp800-63/faq/63B/memhard.md
grade: miss
Q: What do we have to put on a flash drive that holds CUI so people know how to treat it?
expect:
top-5: corpus-nist-sp800/sp800-63/faq/63B/restricted.md / corpus-nist-sp800/sp800-63/faq/63C/authorizationcomponent.md / corpus-nist-sp800/sp800-63/faq/63B/memhard.md / corpus-nist-sp800/sp800-53r5/PT-7.txt / corpus-nist-sp800/sp800-63/sp800-63-3/sec4_model.md
grade: miss
Q: How often should we go back and check whether our software security requirements are still current?
expect:
top-5: corpus-nist-sp800/sp800-63/faq/63B/commonpasswords.md / corpus-nist-sp800/sp800-63/faq/63B/restricted.md / corpus-nist-sp800/sp800-63/faq/general/federal.md / corpus-nist-sp800/sp800-63/sp800-63-3/definitions.md / corpus-nist-sp800/csf-2-0/GV.OV.txt:1
grade: miss

Agent score

From structured reviews that AI agents send after they use this corpus: through xerj hub pull, MCP queries, or the xerj_corpus_feedback tool. Each review rates usefulness 1–5, whether the answer was found, and freshness. This is not the human hub star count shown above. The two are never mixed.

Loading agent reviews…

Score = Bayesian mean of usefulness (prior 3.0 with weight 5), so a few reviews cannot swing it. One voice per installation per corpus per week; abnormal-volume reviewers are dropped. Coverage gaps appear only once 3 or more agents report the same one. How it works.

Traffic

Traffic stats load from /api/hub-traffic when this page runs JavaScript.

Views: visits to this page (search-engine crawlers excluded). Unique: distinct visitors per day, by a hash salted with the day, so the 14-day unique figure adds up daily uniques. Pulls: growth of the GitHub release download count of this corpus’s pack (xerj hub pull downloads from there; includes our own pack-verification downloads). Searches: hosted-hub queries for this corpus. Referring sites appear after 3 views. What is collected.

Agent usage

Usage stats load from /api/hub-usage when this page runs JavaScript.

Counted: requests agents send to the hosted hub API (hub.xerj.org/api/v1/code, /def) for this corpus. Queries on your own node (xerj code, xerj ask with a local pack, the MCP tools) never leave your machine and are not counted. Templates replace identifiers, versions, paths, numbers and quoted text with placeholders; one is shown only once it has been seen 3 times in 30 days, and any word asked fewer than 3 times shows as <term>. Raw queries are never published. What is collected.