Skip to content

Enhance container registry security guidelines #101

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.

Sign up for GitHub

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

Open
syedDS wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Enhance container registry security guidelines #101

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...ion/2-Process/2-3-Build/2-3-3-Container-Security/2-3-3-2-Container-Hardening.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ Utilize security features provided by container runtimes, such as SELinux, AppAr
- **Monitor Container Activity**
Implement logging and monitoring mechanisms to detect and respond to security incidents. Monitor container behavior, access logs, and system logs to identify any suspicious activity.

- **Secure Container Registry**
Protect container images by securing the container registry. Implement authentication, access controls, and encryption to ensure that only authorized users can access and modify container images.
- **Secure Container Registry and supply chain**
Protect container images by securing the container registry. Implement authentication, access controls, and encryption to ensure that only authorized users can access and modify container images. Thus, enforce image signing and verification (with Notary, Sigstore) and only allow deployment of signed, policy‑compliant images from approved registries into production environments

---

Expand Down