Maha Policy · governed federation

NIST CSRC assurance-case glossary — Authority scope

NIST CSRC assurance-case glossary — Authority scope is implemented as a source-bounded authority scope guide.

Active canonical release · fedrelease_b037458b43b9fa44fd684b120b678fa5 · exact revision sha256:a3a798fe53384be080cac01f20a127cf824ffb8aba1fa1929ddb002f265ea354

answer

Direct answer

NIST CSRC assurance-case glossary — 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 CSRC assurance-case glossary — https://csrc.nist.gov/glossary/term/assurance_case — definitions and identified source documents. Supports: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

limitations

What the evidence does not establish

A glossary definition is not current law and does not show that a particular assurance case is adequate.

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-assurance-case

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: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

It must preserve the recorded boundary: A glossary definition is not current law and does not show that a particular assurance case is adequate.

required-by-specification

Exact locator

This exact locator section is constrained to the same inspected scope: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

It must preserve the recorded boundary: A glossary definition is not current law and does not show that a particular assurance case is adequate.

required-by-specification

What this source supports

This what this source supports section is constrained to the same inspected scope: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

It must preserve the recorded boundary: A glossary definition is not current law and does not show that a particular assurance case is adequate.

required-by-specification

What this source does not establish

This what this source does not establish section is constrained to the same inspected scope: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

It must preserve the recorded boundary: A glossary definition is not current law and does not show that a particular assurance case is adequate.

required-by-specification

Related definitions and applications

This related definitions and applications section is constrained to the same inspected scope: Defines an assurance case as auditable argument and evidence with explicit assumptions supporting specified claims.

It must preserve the recorded boundary: A glossary definition is not current law and does not show that a particular assurance case is adequate.

bounded answers

Questions this page can answer

What source is being inspected?

NIST CSRC assurance-case glossary — Authority scope is implemented as a source-bounded authority scope guide.

Where exactly is the relevant material?

NIST CSRC assurance-case glossary, https://csrc.nist.gov/glossary/term/assurance_case — definitions and identified source documents

What claims can this source support?

A glossary definition is not current law and does not show that a particular assurance case is adequate.

What rights and reuse limits apply?

derived-from: urn:maha:source:t20-nist-assurance-case 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.