Maha Policy · governed federation

NIST AI 600-1 and NIST SP 800-171r3 — Authority scope

NIST AI 600-1 and NIST SP 800-171r3 — Authority scope is implemented as a source-bounded authority scope guide.

Active canonical release · fedrelease_007116be796cd48966fac99e99690c4c · exact revision sha256:d51c38b27b88ca820ae882e5e0b79755376607adff2ba23dda51866167249316

answer

Direct answer

NIST AI 600-1 and NIST SP 800-171r3 — Authority scope is implemented as a source-bounded authority scope guide.

method

Answer contract

Apply the authority scope lens only to the exact inspected source scope; do not infer authority from adjacent topics.

evidence

Evidence and exact locators

NIST AI 600-1 and NIST SP 800-171r3 — https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf — MAP 5.1; https://nvlpubs.nist.gov/nistpubs/SpecialPublications/800-171r3/NIST.SP.800-171r3.html — 03.06.01–03.06.03. Supports: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

limitations

What the evidence does not establish

Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

rights

Rights and reuse

official-public-reference; quote-free metadata and paraphrase only

relationships

Dependencies and related concepts

derived-from: urn:maha:source:t20-nist-incident

governed-by: urn:maha:concept:evidence:source-identity

limits: urn:maha:concept:interpretation

required-by-specification

Source identity and provenance

This source identity and provenance section is constrained to the same inspected scope: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

It must preserve the recorded boundary: Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

required-by-specification

Exact locator

This exact locator section is constrained to the same inspected scope: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

It must preserve the recorded boundary: Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

required-by-specification

What this source supports

This what this source supports section is constrained to the same inspected scope: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

It must preserve the recorded boundary: Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

required-by-specification

What this source does not establish

This what this source does not establish section is constrained to the same inspected scope: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

It must preserve the recorded boundary: Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

required-by-specification

Related definitions and applications

This related definitions and applications section is constrained to the same inspected scope: Describes incident inputs, tracking, reporting, response, testing, and the dependence of reporting details on law, policy, sensitivity, and organizational assignment.

It must preserve the recorded boundary: Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

bounded answers

Questions this page can answer

What source is being inspected?

NIST AI 600-1 and NIST SP 800-171r3 — Authority scope is implemented as a source-bounded authority scope guide.

Where exactly is the relevant material?

NIST AI 600-1 and NIST SP 800-171r3, https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf — MAP 5.1; https://nvlpubs.nist.gov/nistpubs/SpecialPublications/800-171r3/NIST.SP.800-171r3.html — 03.06.01–03.06.03

What claims can this source support?

Cybersecurity controls and voluntary AI guidance do not establish a universal mandatory AI-incident regime.

What rights and reuse limits apply?

derived-from: urn:maha:source:t20-nist-incident governed-by: urn:maha:concept:evidence:source-identity limits: urn:maha:concept:interpretation

What inference must a reader or machine refuse?

A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.