For developers
Build secure software without changing how you work.
Sentrasec runs where your code already goes: the terminal, the pipeline, your editor. Findings that need action arrive with a remediation plan and a test plan your coding agent can carry out.
One command, every surface
A single scan covers source, secrets, dependencies, infrastructure definitions and containers, with DAST for running apps: no separate tool per concern.
- SAST
- Secrets
- SCA
- IaC
- Container
- DAST
$ sentrasec scan .$ sentrasec scan . --scanners sast,secrets,sca$ sentrasec scan . --format sarif > results.sarifResults are deduplicated across scanners before they are reported, so one underlying issue found three ways is one finding, not three.
The workflow
Security runs on the path the code already takes, at the point where changing it is cheapest.
- git push
- CI
- sentrasec scan
- Triage
- Remediation plan
- Merge
No new dashboard
With SARIF uploaded to GitHub code scanning, a finding shows up on the lines that caused it. If nothing is wrong, nothing interrupts you.
Fails only when it should
Gating uses a severity threshold and rule overrides you set, so the build breaks on what you decided is blocking and not on everything.
Same results locally
The engine in CI is the engine on your machine. You can reproduce and clear a finding before you push.
Workspace Chat
Ask about a finding instead of researching it.
Every finding is connected to the rule, weakness class and remediation behind it, so the follow-up questions have answers already.
Explain finding
What the rule matched, the path it followed, and why it matters here.
Remediation plan
The change to make, the files, endpoints and tests it touches, and the test plan that proves it.
Explain rule
What the detection tests for, and when it legitimately does not apply.
Explain CVE
Affected ranges, exploitation conditions and the upgrade that resolves it.
Explain CWE
The underlying weakness class, separate from this particular instance.
Explain OWASP
How the finding maps to the category your programme reports against.
Or stay in your editor
Through MCP, your coding agent can read your findings and their remediation plans without you leaving the file you are working in. The agent makes the change and runs the tests.
$ claude mcp add sentrasec -- sentrasec mcpClaude Code, Cursor, Codex, Windsurf, GitHub Copilot and VS Code all connect over the same interface. The agent discovers the available tools and picks the right one from a plain-language request.