1. Home
  2. FedRAMP
  3. AU-10

BRACKETOLOGY | FEDRAMP

AU-10: NON-REPUDIATION

  • FedRAMP Baseline Membership AU-10:
  • HIGH

FedRAMP Bracketology

Use the FedRAMP Control Membership information above to determine if a control or control enhancement is required for each Impact Baseline — LOW, MODERATE, or HIGH

Click on the panel below each control or control enhancement to review the FedRAMP Impact Baseline-specific control configuration requirements for each of the [BRACKETS] in each control and/or control enhancement.

Review and use Additional Requirements and Guidance to build FedRAMP-compliant controls for your risk-based cybersecurity program.

To change the baseline view in the panel, click on LOW, MODERATE, or HIGH when the panel is open

Panels only appear where there are [BRACKETS] in the control or enhancement or where there is FedRAMP-specific requirements or guidance available.

The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed [Assignment: organization-defined actions to be covered by non-repudiation].

Click Low | Moderate | High below to see FedRAMP control configuration information. It's in BOLD.

There are no FedRAMP-specific requirements if this control is used for a LOW Impact system.

There are no FedRAMP-specific requirements if this control is used for a MODERATE Impact system.

The information system protects against an individual (or process acting on behalf of an individual) falsely denying having performed minimum actions including the addition, modification, deletion, approval, sending, or receiving of data to be covered by non-repudiation.

SUPPLEMENTAL GUIDANCE

Types of individual actions covered by non-repudiation include, for example, creating information, sending and receiving messages, approving information (e.g., indicating concurrence or signing a contract). Non-repudiation protects individuals against later claims by: (i) authors of not having authored particular documents; (ii) senders of not having transmitted messages; (iii) receivers of not having received messages; or (iv) signatories of not having signed documents. Non-repudiation services can be used to determine if information originated from a particular individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Organizations obtain non-repudiation services by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts).

CONTROL ENHANCEMENTS

AU-10 (1) NON-REPUDIATION | ASSOCIATION OF IDENTITIES

The information system:

    • (a) Binds the identity of the information producer with the information to [Assignment: organization-defined strength of binding]; and
    • (b) Provides the means for authorized individuals to determine the identity of the producer of the information.

Supplemental Guidance:

This control enhancement supports audit requirements that provide organizational personnel with the means to identify who produced specific information in the event of an information transfer. Organizations determine and approve the strength of the binding between the information producer and the information based on the security category of the information and relevant risk factors.

RELATED CONTROLS: AU-10 (1)

AU-10 (2) NON-REPUDIATION | VALIDATE BINDING OF INFORMATION PRODUCER IDENTITY

The information system:

    • (a) Validates the binding of the information producer identity to the information at [Assignment: organization-defined frequency]; and
    • (b) Performs [Assignment: organization-defined actions] in the event of a validation error.

Supplemental Guidance:

This control enhancement prevents the modification of information between production and review. The validation of bindings can be achieved, for example, by the use of cryptographic checksums. Organizations determine if validations are in response to user requests or generated automatically.

RELATED CONTROLS: AU-10 (2)

AU-10 (3) NON-REPUDIATION | CHAIN OF CUSTODY

The information system maintains reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released.

Supplemental Guidance:

Chain of custody is a process that tracks the movement of evidence through its collection, safeguarding, and analysis life cycle by documenting each person who handled the evidence, the date and time it was collected or transferred, and the purpose for the transfer. If the reviewer is a human or if the review function is automated but separate from the release/transfer function, the information system associates the identity of the reviewer of the information to be released with the information and the information label. In the case of human reviews, this control enhancement provides organizational officials the means to identify who reviewed and released the information. In the case of automated reviews, this control enhancement ensures that only approved review functions are employed.

RELATED CONTROLS: AU-10 (3)

AU-10 (4) NON-REPUDIATION | VALIDATE BINDING OF INFORMATION REVIEWER IDENTITY

The information system:

    • (a) Validates the binding of the information reviewer identity to the information at the transfer or release points prior to release/transfer between [Assignment: organization-defined security domains]; and
    • (b) Performs [Assignment: organization-defined actions] in the event of a validation error.

Supplemental Guidance:

This control enhancement prevents the modification of information between review and transfer/release. The validation of bindings can be achieved, for example, by the use of cryptographic checksums. Organizations determine validations are in response to user requests or generated automatically.

RELATED CONTROLS: AU-10 (4)

AU-10 (5) NON-REPUDIATION | DIGITAL SIGNATURES

[Withdrawn: Incorporated into SI-7].

REFERENCES:

  • NO REFERENCES