# Scanning container images for a Canadian client

**URL:** <https://anchorecommunity.discourse.group/t/scanning-container-images-for-a-canadian-client/673>\
**Category:** General\
**Created:** [November 16, 2026, 2:28pm UTC](https://anchorecommunity.discourse.group/t/scanning-container-images-for-a-canadian-client/673 "2026-11-16T14:28:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![4GoodHosting](https://yyz2.discourse-cdn.com/free1/user_avatar/anchorecommunity.discourse.group/4goodhosting/32/535_2.png) [@4GoodHosting](https://anchorecommunity.discourse.group/u/4GoodHosting)\
**Post date:** [November 16, 2026, 2:28pm UTC](https://anchorecommunity.discourse.group/t/scanning-container-images-for-a-canadian-client/673/1 "2026-11-16T14:28:00Z")

</div>

I’m setting up container image scanning for a small business in Canada that runs a few web apps holding customer records. PIPEDA covers most private businesses here, and BC public bodies and Quebec’s Law 25 add stricter rules about where personal information is stored, so the servers, registry and scan results will all stay in a Canadian data centre. This is my plan with Syft and Grype:

1. **SBOMs:** generate an SBOM with Syft for every image at build time and store it next to the image.
2. **Scanning:** run Grype in CI and fail the build on critical vulnerabilities that have a fix available.
3. **Database updates:** keep the Grype vulnerability database updated daily on the CI runner.
4. **Ignore rules:** a reviewed ignore file for false positives, with a reason and an expiry date for each entry.
5. **Registry:** a private registry hosted in Canada, rather than a public one.
6. **Rescans:** a nightly rescan of images already running in production against the latest database.
7. **Reports:** keep scan results for a set period as evidence for client security reviews.

For those using Syft and Grype day to day: how do you manage ignore rules across many repos, and do you scan from SBOMs or from the images themselves?
