Secrets
Native secret detection in repository source, with configurable validation and history scanning.
Interdict /Native detection
Repository analysis, connected to the bigger picture.
Explore the detection and inventory capabilities that feed Interdict’s security graph.
Native detectionStart with the source.
Start with the source.
Keep the context.
Interdict combines its own repository analysis with findings from supported security tools. Detection, inventory, and relationships feed the same review workflow.
Code security
Native static analysis for language-aware detection, cross-file dataflow, and reachability evidence.
Infrastructure as code
Review configuration in Terraform, CloudFormation, Kubernetes, Helm, Kustomize, and Dockerfiles.
Cryptography
Collect cryptographic inventory and review the algorithms and operations present in supported source.
API discovery
Discover supported application routes and review recorded authentication and sensitive-data context.
Dependencies
Match discovered packages to public vulnerability advisories and review published fixed versions.
Coverage depends on supported languages, configured tools, enabled rules, and completed collection. Cryptographic inventory is a beta capability.
Questions, answered
Know what you’re evaluating.
Explore supported sources, collection requirements, and the review workflow.
Does Interdict replace our existing scanners?
Interdict includes native repository analysis and can ingest supported external findings. You can use both; connector and language coverage should be checked against your environment.
Does a high priority score prove exploitation?
No. Priority brings together available evidence to support triage. Reachability, exposure, AI assessments, and confirmed exploitation are different things; missing evidence remains unknown.
Can scanning run in our environment?
Outposts execute scanning and connector work near your systems. Collection and upload behavior depends on workflow and configuration; private execution is not a promise that no data leaves the environment.
What happens after a finding is reviewed?
Teams can assign work, manage exceptions and policies, and track remediation attempts. An approved exception, merged change, and verified fix remain distinct outcomes.
How do we get started?
Access options to discuss your repositories, supported sources, deployment needs, and intended workflow. The team can help assess whether the current product fits your requirements.
