-
Notifications
You must be signed in to change notification settings - Fork 110
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
Security scanning for SSB/SOLR (test) #3799
Comments
Falco installed on a test EKS cluster in staging, Time to config it.
|
@FuhuXia continuing on it for now. |
Events were generated when suspicious commands were run on new containers
logs:
logs: |
This is SO GREAT. Please make the Slack webhook URL a variable when you add this to the Terraform. |
Still need to create custom rule specific for Solr classic/cloud security. |
Will put on hold for the time being pending ECS work. |
Moving back to Icebox for now |
This is not important for data.gov anymore because of Solr on ECS, But the scanning mentality would still be useful for other EKS applications. This is a good historical ticket, but I don't think any more work will be done here. |
User Story
In order to meet SI-3, data.gov security wants a scanning tool performing scanning and alerting on malware/any unexpected file system changes.
Acceptance Criteria
[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]
WHEN an unexpected/bad file is added to the SOLR container
THEN an alert is generated
Background
Related to #3797, would replace the necessity of regular SOLR restarts.
Security Considerations (required)
Related to SI-3.
Sketch
This may change, but current plan is to:
helm install
from your shell, and testing it outhelm_release
resource to the Terraform in the EKS brokerpak's provision-k8s directory to automate thatThe text was updated successfully, but these errors were encountered: