Workload Protection Engine
varunjain99 opened this issue · 0 comments
varunjain99 commented
Workload Protection Planning
Broad overview of the proposed engine
- Visibility: Determine running compute and the corresponding volumes to be snapshotted
- Much of this is done through cartography?
- TODO: Figure out what needs to be snapshotted for container/serverless based compute
- Snapshot block storage for analysis
- Snapshots should be deleted when they are no longer needed
- Mount snapshots onto an EC2 to do analysis
- Different file systems may need to be dealt with differently
- Container file systems may need to be reconstructed
- TODO: Figure out which filesystems and how you mount different filesystems
- TODO: Figure out for container/serverless how you reconstruct their filesystems
- Workload analysis
- Many possible types of analysis
- Vulnerability scanning
- App configuration analysis
- Malware analysis
- Secrets / Access key / password analysis
- Sensitive data analysis
- Probably should do vuln analysis and / or secret analysis first?
- TODO: Which open source scanning tools should we use?
- TODO: Should we pickup container networking in this step? Or is that separate?
- Many possible types of analysis
- Add workload analysis findings to Neo4j db
- Delete any ec2 / snapshots that were created