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

Fix: #37. Add ContainerImageAnalysis kb. #38

Merged
merged 2 commits into from
Jan 9, 2024

Conversation

ioggstream
Copy link
Contributor

@ioggstream ioggstream commented May 12, 2022

This PR

  • adds ContainerImage Analysis

Fixes: #37

@netfl0
Copy link
Contributor

netfl0 commented May 17, 2022

In the kb-article it was noted to scan for weak configurations (we do have D3-ACH for fixing the problems discovered) and vulnerable libraries (D3-SU is the fix here). Those are distinct countermeasures we should probably break out. Given that applications are inside the containers and other package formats, we may need to break this out to make sure its obvious which one to select. We are working on vulnerability scanning / inventory, tagging @hack-sentinel since he is currently working in this space.

@ioggstream
Copy link
Contributor Author

To address this, we should define whether ContainerImages fall under PlatformHardening or ApplicationHardening.

IMHO:

  • if we deploy a containerized application, then the whole container is probably the deliverable, and the container image should be treated like software libraries;
  • if we deploy a containerized system functionality, then D3-SU is probably corret.

@netfl0 netfl0 merged commit 6b5fa4c into d3fend:develop Jan 9, 2024
1 check passed
@ioggstream ioggstream deleted the ioggstream-37 branch January 10, 2024 08:59
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

Successfully merging this pull request may close these issues.

ContainerImageAnalysis < FileAnalysis, ApplicationHardening
2 participants