Enrichment Strategies

Each piece of collected evidence undergoes normalization and classification. Language is detected and content is cleaned to eliminate false positives from formatting issues or irrelevant matches. When credentials, keys, or tokens are identified in code or web pages, the enrichment process cross-checks them against known brand domains, employee emails, or infrastructure patterns to confirm the likelihood of real exposure.

In cases involving domains or subdomains, WHOIS metadata, certificate transparency records, and DNS responses are added to determine whether the asset is newly registered, active, and potentially malicious. Additionally, all suspicious domains are validated against the Inopli internal threat feed and public phishing repositories to confirm known malicious infrastructure and reduce false positives. This step enhances the ability to quickly identify phishing threats and supports prioritization based on confirmed reputation signals.

When findings involve cloud storage, enrichment confirms whether the exposed content is publicly accessible, identifies the cloud provider, and examines the filenames and content types to highlight sensitive data such as internal documentation, logs, or customer information.

For public code repositories, commit metadata and author information are included to support traceability. Findings are enriched with indicators such as repository visibility, timestamps, and file paths to help prioritize which exposures require immediate attention.