Integrations

Security sensors

Understand supported scanners, execution boundaries, rollout states, and cross-tool finding deduplication.

Veriom brings security observations into the same architecture review as repository and infrastructure evidence. Each finding retains its source, location, audit revision, and coverage context.

Many scanners, one evidence vocabularyIsolated tools produce observations that are normalized and deduplicated before architecture relevance is decided.VERIOM FIELD GUIDEEVIDENCE FIRSTMany scanners, one evidence vocabularyIsolated tools produce observations that are normalized and deduplicated before architecture relevance is decided.TB1TB2SCANNERSEVIDENCEREVIEWcorrelateadjudicate01Core sensorsCode · Secrets · Dependencies02Extended sensorsConfiguration · Corroboration03Normalize findingFingerprint + provenance04Cross-tool dedupeOne issue, many signals05Architecture impactRelevant · excluded · unknownA failed sensor creates a coverage gap; it cannot create a clean verdict.
Many scanners, one evidence vocabulary

Review coverage

An audit shows which evidence was collected, which checks completed, and where coverage is missing. An incomplete assessment remains visible as a gap. An empty findings list does not establish that an unassessed system is secure.

One issue, all of its sources

When independent observations share a reviewed advisory identity, Veriom presents one finding with the contributing evidence. It preserves corroboration and source locations.

Rules remain separate unless they share a reviewed deterministic identity. Similar titles and model judgement are not sufficient to merge findings.

Each canonical finding retains:

  • the strongest supported risk representation;
  • the original evidence and source identifiers;
  • source locations and the assessed revision;
  • first-seen and last-seen history;
  • relevant coverage gaps.

Permission boundaries

Repository reviews inspect captured source. Customer-connected infrastructure and runtime evidence require separately scoped access. A repository connection does not grant permission to access a cloud account or an active target.

Read the security controls or request a security review.

Was this guide useful?

Your response stays in this browser unless you open a GitHub issue.
View source