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

[Feedback]: Guidance should include the responsible-party assembly for CSP Name #747

Closed
1 of 12 tasks
vmangat opened this issue Oct 1, 2024 · 2 comments · Fixed by GSA/automate.fedramp.gov#112
Closed
1 of 12 tasks

Comments

@vmangat
Copy link

vmangat commented Oct 1, 2024

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 guidance need to be updated to include a responsible-party assembly tying the CSP party to the role-id "cloud-service-provider"

Where, exactly?

https://automate.fedramp.gov/documentation/ssp/4-ssp-template-to-oscal-mapping/
image

Other information

No response

@aj-stein-gsa
Copy link
Contributor

Hi @vmangat, I was reviewing the backlog for items marked triage needed and this request was very timely. It is not just for CSP, but given your request, I believe we are in the process of resolving this by updating a constraint and associated documentation for #874 in GSA/automate.fedramp.gov#112. Stay tuned. I will mark this issue as in review, as it will be closed with the #112 PR potentially.

@aj-stein-gsa aj-stein-gsa moved this from 🆕 New to 📋 Backlog in FedRAMP Automation Nov 15, 2024
@aj-stein-gsa aj-stein-gsa moved this from 📋 Backlog to 🔖 Ready in FedRAMP Automation Nov 15, 2024
@aj-stein-gsa aj-stein-gsa self-assigned this Nov 15, 2024
@aj-stein-gsa aj-stein-gsa linked a pull request Nov 15, 2024 that will close this issue
@aj-stein-gsa aj-stein-gsa moved this from 🔖 Ready to 👀 In review in FedRAMP Automation Nov 15, 2024
@aj-stein-gsa
Copy link
Contributor

I will be marking this issue as ready to ship and complete as resolved by cross-linked issue #874.

@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in FedRAMP Automation Nov 18, 2024
@aj-stein-gsa aj-stein-gsa moved this from ✅ Done to 🚢 Ready to Ship in FedRAMP Automation Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants