Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify OMB M-07-16 and relevance to PII "rolodex" exception for business contact info in party/role bindings #155

Open
3 tasks
aj-stein-gsa opened this issue Jan 25, 2025 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@aj-stein-gsa
Copy link
Contributor

User Story

As a security practicioner using OSCAL-enabled tools or software developer that programs them, in order to be sure I give required information in accordance with government, GSA, and FedRAMP policies with sufficient clarity and the most minimal risk, I would like clear documentation as to whether FedRAMP's requirements around OSCAL for contact information and party for certain parties and roles in a Digital Authorization Package are PII or not.

Goals

  • Clarify how FedRAMP use of OSCAL requires, in some cases, collection information about persons, but it is not PII.
  • Provide reference information to the OMB policy, OMB M-07-16, and in particular footnote 6 on page 1, explaining how GSA complies with this OMB policy and OSCAL must reflect that

Dependencies

N/A

Acceptance Criteria

  • A PR to the website with an informational or warning modal box explaining the rolodex exception and linking to OMB M-07-16.

Other information

No response

@aj-stein-gsa aj-stein-gsa added the documentation Improvements or additions to documentation label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant