Application security for source code

Aegis

The code that builds the estate.

It scans your source code and infrastructure as code for security defects and exposed secrets, with one record of findings and a software bill of materials. Run it over a checkout or in your own CI. A supplied deployment mapping links findings to workloads, and anything it cannot check or link stays visible as a gap.

The vast curved concrete wall of a hydroelectric dam at night, lit in cold blue floodlight.The vast curved concrete wall of a hydroelectric dam on a bright, clear day.

The film · 1:03

Seven scanners in, one record of findings out.

The film shows Aegis's seven-scanner service workflow: one shape for every finding, and a finding stays open until a scanner that finished says it is gone. Engagement scans use the license-reviewed subset described below.

Music and on-screen text, no narration; the captions describe the music and sound and are off until you turn them on. Every scene is a drawn illustration, marked as one, on sample data. The service workflow shows code excerpts; engagement exports omit them and use a location-based fingerprint. The hash and the finding's four scans come from Aegis's own code.
Read the film’s text version

Title: Aegis. Seven scanners, one record of findings. 2026. A bright, energized electronic score runs under the whole film, with a soft effect on each card, timer, and click.

Seven reports: Seven document tiles land one a beat, one for each of Semgrep, Bandit, pip-audit, Safety, detect-secrets, Checkov, and Trivy, each laid out differently: “Seven reports. Seven shapes.”

One record: “Aegis runs all seven.” The seven names land in a row and a ledger frame draws beneath them, with columns for scanner, rule, severity, file, and status. The line becomes “One record of findings.”

A scan: As the beat drops, a sample repository is registered and scanned with two calls: POST /api/v1/repos and POST /api/v1/repos/{id}/scan. “Each scanner gets a clock”: seven lanes, each with a ring the size of its time limit, five minutes each and two for Safety, so Safety's ring is the short one. Six finish, and in this illustration Checkov times out: “One times out. The rest keep going.” The tallies end at 6 finished and 1 timed out.

One shape: “Every result, one shape.” A Semgrep, a Bandit, and a pip-audit result arrive in their own JSON shapes and become three cards of one shape: severity, scanner and rule, file and line, and a fix when the scanner offers one (Bandit's card says none offered). Bandit's HIGH is raised to CRITICAL for rule B602, with the override line from its mapping file typed out. Then “Five severities. Critical to info.” and CRITICAL, HIGH, MEDIUM, LOW, and INFO land one a beat.

A hash: “Every finding gets a hash.” Three lines of the flagged code, each behind the line number Bandit gives it, sit beside the finding's dedup hash, shown as its first and last four characters. The code moves four spaces right, as a formatter would, and the hash does not move: “Reindent it. Same row.” The formula reads sha256 of scanner, rule_id, file_path, normalized code, and severity.

A finding has a life: As the beat drops again: “A finding has a life.” Four scans run left to right along a timeline, each marked only by whether Bandit finished, and the same critical B602 finding follows them: open and new on scan 1; fixed on scan 2, because Bandit finished and the finding is gone; open again and reopened on scan 3, the same row; and on scan 4 Bandit times out, so its findings stay open, with a lock. “Fixed only if the scanner finished.” An amber ring pulses around the last card.

An engine and an API: “An engine and an API.” A request, GET /api/v1/findings?severity=CRITICAL, is typed out, nine findings land in a list, and the list narrows to the three critical ones, 3 of 9 rows. A dashboard outline fades in and a strike crosses it out: “No dashboard.”

Close: “Seven scanners.” and “One record of findings.” land on the beat while the seven scanner names drop into a ledger.

End card: The Aegis mark, the name, “Seven scanners, one record of findings.”, and the address acudef.com/aegis, on the final chord.

What it does

How it works.

  1. Scans a checkout.

    Run it from Vantalect's environment or your own CI, without a database, queue, or hosted scanning service. Your checkout stays unchanged, and an offline option keeps the scan off the network.

  2. Runs reviewed scanners.

    Bandit checks code, detect-secrets checks for exposed secrets, and Checkov checks infrastructure as code. Semgrep uses local rules supplied by the operator. A reviewed inventory gates the bundled engines, rule sets, and advisory feeds; scanners with blocked or unverified entries stay off.

  3. Exports findings and their gaps.

    One model carries severity, CWE, file and line, fix guidance when offered, and a deduplication fingerprint, alongside a CycloneDX 1.5 software bill of materials. Machine-readable findings and application-security facts feed the report. Skipped or failed scanners, missing dependency data, and joins it cannot make are recorded as gaps.

  4. Links code to workloads.

    A deployment mapping you supply connects findings to workloads by repository path, IaC resource, or image digest. Missing mappings and unmatched findings are gaps. A path match records the supplied assignment; it does not prove that code runs there. Container findings come from image reports you supply.

  5. Signs the CI handoff.

    The CI runner signs its output. An offline check against a trusted public key detects changed, missing, or extra files and validates the application-security facts with the survey engine. CI output awaits that validation; a signature proves origin and integrity under the trusted key, not that a scan was honest.

  6. Keeps source excerpts out of exports.

    Engagement findings carry rule descriptions and file locations instead of source excerpts or messages quoting matched code. The secret detector reports fingerprints instead of matched values. A final check refuses output containing a guarded secret value.

By design

What it never does.

  • Connects to a cloud account.
  • Writes to your checkout.
  • Runs a scanner with blocked or unverified license entries for an engagement.
  • Treats a missing workload link or a skipped scanner as a clean result.
  • Pulls or builds container images. It reads image reports you supply.

Footprint

What it touches in your organization.

Your accounts
None. It never connects to a cloud account.
Your code
Read access to a checkout of the repositories you grant. Scanners run over a temporary copy, with repository-supplied scanner configuration removed and the changes recorded. The original checkout stays unchanged.
Where it runs
In Vantalect's environment or your own CI. Neither form needs a connection to an Acumen system.
What you supply
A deployment mapping for workload links, local rules for Semgrep, and image reports for container findings. The signed CI workflow also needs a signing key and a separately trusted public key for verification.
Where the data lives
Output stays where the operator writes it, with Vantalect holding engagement evidence under the engagement terms. Acumen Defensive receives none of it.
Compare every tool’s footprint

In Vantalect’s engagements

Where it fits.

  • AWS Security, Compliance & Governance Audit: Aegis is the companion tool. The application-security tool joins when the statement of work includes your IaC and pipeline code; continuous assessment keeps the gate measured afterward, and external testing proves what the audit found.
  • AWS Well-Architected Framework Review: Aegis is the companion tool. The application-security tool reads the reviewed workload's code.

Put the tools to work

Engagements run through Vantalect.

Acumen Defensive builds the tools and runs no engagements of its own. Vantalect delivers every engagement that uses them, with the scope and price of each published at vantalect.com.

Start an engagement at vantalect.com

Vantalect, LLC is a separate company that licenses and operates these tools.