Secret/PII Scan
Secret/PII Scan connectors connect OX to tools that detect exposed secrets (API keys, tokens, passwords) and personally identifiable information (PII) in source code, configuration files, and repositories
OX imports data from these tools through APIs, enriches it with OX context (application mapping, ownership, workflows, and compliance), and presents it alongside findings from other scanners and tools in a unified view.
What OX adds
Context and correlation: OX maps findings to applications, services, and teams to show impact and ownership.
Prioritization with severity factors: OX may reprioritize scanner severities when exploitability and environment context reduce risk (for example, Critical → High). Severity factors explain why the priority changed.
Evidence at a glance: When available, OX displays scanner evidence, file locations, and remediation guidance alongside OX analytics to speed triage.
Where data appears in OX
Active Issues: Filter by Source tool to focus on findings from a specific connector.
Issue details: Tabs show scanner evidence, asset data, and OX correlations such as application and repository mapping.
Assets and applications: Imported assets appear in asset views, application context, and dashboards.
Risk prioritization: Findings are ranked using combined development, pipeline, and runtime signals.
Supported connectors
Fortify on Demand
Fortify Software Security Center
GitGuardian
GitHub Secret Detection
GitLab Secret Detection
HCL AppScan
OX Secret/PII Scan
Semgrep Enterprise
Wiz CLI Secrets: OX supports multiple Wiz connectors. For setup instructions, see the article Wiz in the Cloud Context folder.
Last updated
