Code security that proves what it finds.
IronBee scans the default branch of your repositories on a schedule. With execution on, it runs your code in a sandbox and calls a finding confirmed only after it reproduced it.
[ Proof ]
It runs the code before it calls it a vulnerability.
What it reproduces is confirmed and gets a severity. What it cannot prove stays a lead.
[ The record ]
Every record shows the way in, and the way out.
The entry point, each step through the code, the line that gives way, and the fix.
Scroll sideways for the whole drawing.
[ When it scans ]
The whole branch once. After that, only what changed.
On the schedule you pick, or by hand. You see the price before a scan starts, and a week with no change costs nothing.
Scroll sideways for the whole drawing.
[ Profile ]
Choose how far it follows a lead.
A deeper profile reads more, takes longer and costs more. Auto picks by the size of the repository, and never picks Deep.
Quick
The fastest scan. It follows fewer leads.
Standard
A broader scan that follows more leads.
Deep
The most thorough scan, and the slowest.
Execution
Off, the code is read. On, it is run to prove a finding.
Scheduled scan
Daily, weekly, every two weeks or monthly.
Paths to ignore
Left out of every scan and of the price.
[ In the console ]
What a scan leaves you with.
Each record stays open until your team accepts it, marks it handled, or calls it not an issue.
3f9e2a1.- If the code changed
- 90 credits
- If nothing changed
- No charge
- Schedule
- Weekly
- Size
- M, 38,412 lines
| Severity | Record | Where | Decision |
|---|---|---|---|
| Confirmed, reproduced by running the code | |||
| High | Any signed-in user can download another account's invoice | internal/http/invoices.go:48 | Open |
| Medium | An uploaded file name can write outside the uploads folder | internal/files/save.go:31 | Accepted |
| Leads to validate, not proven yet, no severity | |||
| Lead | The webhook accepts unsigned events when the secret is empty | internal/hooks/stripe.go:22 | Open |
FAQ
What does it scan?
The default branch of each repository you turn it on for, on GitHub, GitLab or Bitbucket. It is off until an owner or an admin turns it on.
When does it run?
On a schedule: weekly by default, or daily, every two weeks or monthly. An owner or an admin can also start a full scan by hand. It does not run on pull requests.
What is the difference between a confirmed finding and a lead?
A finding is confirmed when the scan reproduced it by running the code, and only then does it get a severity. A lead is one it could not prove yet. It comes with what blocks a verdict and how to validate it.
Where does my code run?
Only inside the scan’s sandbox, and only when you turn execution on. The scan reaches the package registries while it installs, and the code it runs has no network beyond itself. It installs Node, Python and Go at the version the repository declares. Other languages are read, not run.
How much does a scan cost?
Credits, by the size of the repository and the profile, from the same monthly pool as code review and verification. The price is shown before a scan starts, and a scan that fails costs nothing.
Who can see the records?
Owners and admins of the account.
Does it comment on pull requests?
No. Code security scans the default branch and keeps its records in IronBee. Pull requests are read by code review.
Can't find your answer? Talk to us.