cryptographic Modules - DIT: How to identify Source and Destination

[Telos-sa]

This is a ...

request - need something additional provided

This relates to ...

• the FedRAMP OSCAL Registry
• the FedRAMP OSCAL baselines
• the Guide to OSCAL-based FedRAMP Content
• the Guide to OSCAL-based FedRAMP System Security Plans (SSP)
• the Guide to OSCAL-based FedRAMP Security Assessment Plans (SAP)
• the Guide to OSCAL-based FedRAMP Security Assessment Results (SAR)
• the Guide to OSCAL-based FedRAMP Plan of Action and Milestones (POA&M)
• the FedRAMP SSP OSCAL Template (JSON or XML Format)
• the FedRAMP SAP OSCAL Template (JSON or XML Format)
• the FedRAMP SAR OSCAL Template (JSON or XML Format)
• the FedRAMP POA&M OSCAL Template (JSON or XML Format)
• the FedRAMP OSCAL Validations

What is your feedback?

The content in the automate fedramp guidance does not include how to handle data in transit elements where there is a source and a destination with the same reference number. Need to understand how this should be represented when there are two different modules in a single record.

Where, exactly?

Guidance for DIT cryptographic modules, and how to identify source and destination, and the connection between the two. Is there supposed to be only 1 entry for DIT? Or should the source and destination each have their own component. If they each have their own component, how are they logicallylinked? Is there a prop for source/destination and a prop to identify the linked source/destination.

Other information

No response