Use current BIMP reports to understand policy coverage, active incident work, and team health.
BIMP reports help you answer concrete questions about tracked repository artifacts. A repository scan describes source state. It does not prove what is currently deployed or provide a compliance certification.
BIMP coverage
Section titled “BIMP coverage”Open Reports, then select Unmanaged base images detected to find images that do not currently have an applicable published mapping.
Use Organization base images detected to review each normalized image, current health, policy status, repositories and branches, and last discovery date.
Select Unmanagable discovered images to find valid Compose service images that depend on environment variables supplied outside the repository. The report preserves the literal image expression, unresolved variable names, repository, branch, file, service, and last discovery date. Because BIMP cannot calculate a trustworthy image identity, these entries are not included in policy, remediation, or artifact-health totals.
Use Digest inventory to compare digest-pinned and tag-only references. Its summary shows verified digests, pinned references, tag-only references, and total references observed in tracked artifacts.
These reports show coverage of supported files on tracked branches. A missing runtime integration, untracked branch, unsupported artifact, or failed scan is outside that coverage.
Investigate unexpected unmanaged results
Section titled “Investigate unexpected unmanaged results”If an image is unexpectedly unmanaged:
- confirm the repository and branch are tracked;
- confirm the latest scan completed;
- check the normalized image shown by the report;
- review applicable Policy Group assignments; and
- compare the source mapping and optional platform scope.
Correct the scan, scope, or mapping, then publish and re-evaluate.
MTTR for incidents
Section titled “MTTR for incidents”Open Reports, then select Current incident to see active image-reference files covered by security-incident remediation. The report includes the incident declaration age, owning team, affected image and artifact, and provider request state.
Use this elapsed time to manage current work. BIMP does not currently calculate historical incident mean time to remediate after requests are completed. Do not present the current age as completed-work MTTR.
MTTR for BAU changes
Section titled “MTTR for BAU changes”BIMP does not currently expose a historical mean time to remediate calculation for routine business-as-usual changes.
Use active remediation state, routine timing, and the remediation grace period to manage current work. If your organization calculates historical MTTR in another system, define its start and finish events explicitly before comparing it with BIMP records.
Team dashboard
Section titled “Team dashboard”Open Reports, then select Organization health by team to review current image-reference health grouped by the team assigned to each repository.
The report shows the number of image-reference files and their health distribution. An unassigned repository cannot contribute to an accountable team view, so assign its team and routine from Repositories.
Use the team report to find where current repository work sits. It does not measure individual developer performance or prove that a changed image has reached production.