Skip to content

Commit

Permalink
Merge pull request MichaelCade#310 from souravsk/main
Browse files Browse the repository at this point in the history
typo
  • Loading branch information
MichaelCade authored Jan 31, 2023
2 parents 9a7879d + d36a1d9 commit d569e37
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions 2023/day23.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,8 @@

In the previous two days we learned why and how to scan container images.

However, usually our infrastucture consists of more than just container images.
Yes, our services wil run as containers, but around them we can also have other artifacts like:
However, usually our infrastructure consists of more than just container images.
Yes, our services will run as containers, but around them we can also have other artifacts like:

- Kubernetes manifests
- Helm templates
Expand All @@ -12,7 +12,7 @@ Yes, our services wil run as containers, but around them we can also have other
For maximum security, you would be scanning all the artifacts that you use for your environment, not only your container images.

The reason for that is that even if you have the most secure Docker images with no CVEs,
but run then on an insecure infrastrucure with bad Kubernetes configuration,
but run then on an insecure infrastructure with bad Kubernetes configuration,
then your environment will not be secure.

**Each system is as secure as its weakest link.**
Expand Down

0 comments on commit d569e37

Please sign in to comment.