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 that ATOs apply to software that's built *and* software that's bought #24

Open
afeld opened this issue Sep 26, 2019 · 1 comment

Comments

@afeld
Copy link
Member

afeld commented Sep 26, 2019

...though an agency may have distinct processes for each.

cc #7

@trevorbryant
Copy link
Contributor

I don't know if this is true for many agencies. Software that's bought (COTS) are reviewed by the Change Control Board and stakeholders to review to proceed to becoming on the agency's software list for approved use.

After then, that engineering task for implementation becomes part of the new A&A process to get authorized for the system to go live.

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