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

Add AMI Report #3

Open
eaddingtonwhite opened this issue May 27, 2016 · 0 comments
Open

Add AMI Report #3

eaddingtonwhite opened this issue May 27, 2016 · 0 comments

Comments

@eaddingtonwhite
Copy link

If devsecops maintained a database/file of public AMI's that have known vulnerabilities/exploits then you could alert a user when they were trying to use in scanned CFN Template. Another Idea would be publishing list of public AMI's devsec ops maintains that are known to be kept up to date with security patches and warning if your not using an approved AMI.

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

1 participant