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

Rename repository #8

Open
trevorbryant opened this issue Mar 24, 2021 · 5 comments
Open

Rename repository #8

trevorbryant opened this issue Mar 24, 2021 · 5 comments

Comments

@trevorbryant
Copy link
Contributor

In the Risk Management Framework and FedRAMP, there is no concept of certifications. Instead, this terminology has been replaced with "authorization".

Strongly recommend renaming the mentions of "certification" to "authorization" to stay consistent with the US Government's vocabulary.

@shawndwells
Copy link
Member

💯 +1

@shawndwells
Copy link
Member

This will totally break many downstream systems. This could be swapped in a major version bump of the schema though.

@trevorbryant
Copy link
Contributor Author

trevorbryant commented Mar 24, 2021

I understand. That's difficult.

Is there any way to track back to see just what it impacts?

Edit: I removed a statement as it seemed harsh when it was not intended to be.

@shawndwells
Copy link
Member

Not really. It's part of the schema, so "whoever uses the schema" would be impacted.

For example, at Red Hat, that would be the entire backend of http://atopathways.redhatgov.io/

@shawndwells
Copy link
Member

Specific example - https://atopathways.redhatgov.io/ato/products/openshift-container-platform-4/NIST-800-53

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants