Forensic Intelligence
In development

Aegis

Ten disciplines. One engagement.

An end-to-end penetration tester and vulnerability scanner for Mac. Discover, test, validate, map and report from one native app, with scope enforcement and approval gates built into the architecture.

For macOS · Native on Apple Silicon · For authorized testing only

Illustration with fictional data. Interface is in development and will change.

10Disciplines, from first scan to retest, in one workspace.
12SQL injection techniques across 7 database backends.
5Report formats: Markdown, HTML, JSON, SARIF and CycloneDX.
0Lines of your source code sent anywhere.

End to end

Ten disciplines. No weak one.

A real assessment is not one tool run once. It is ten kinds of work that have to agree with each other. Aegis does all ten against the same scope, evidence and findings.

Discovery

Network scanning with quick, standard, full and custom port profiles, service detection and OS fingerprinting.

Web and API testing

Checks for SSRF, XXE, path traversal, open redirects, IDOR, CSRF, cross-site scripting and insecure cookies across websites, REST and GraphQL.

Injection

A dedicated SQL injection engine with database fingerprinting, built for the applications that hold the most sensitive records.

Interception

An intercepting proxy with TLS termination, plus detection of SSL stripping and certificate pinning.

Cloud and identity

Validation of cloud configuration and identity controls alongside the application and the network.

Code and dependencies

Secrets detection, dependency auditing, static analysis, infrastructure-as-code checks and SBOM generation.

Exploit validation

Findings are confirmed with controlled proof, so the report lists what is real instead of what a scanner guessed.

Attack paths

Findings are mapped to MITRE ATT&CK and joined into an attack graph that shows how one weakness leads to the next.

Guided autonomy

An operator that plans and runs the next step for you, and stops for your approval before anything that carries risk.

Report and retest

Evidence vault, client-ready reports, remediation tracking and revalidation to prove a fix actually worked.

Proof over assumptions

A finding is not a finding until it is proven.

Scanner output is a list of maybes. Aegis validates each candidate with a controlled check and stores the request, response and result as evidence.

  • Validated findings are clearly separated from unconfirmed ones
  • Evidence is captured as the work happens, not rebuilt afterwards
  • Risk scoring weighs severity and confidence together
  • Fingerprinting tracks the same finding across scans and retests
# Evidence · finding F-014
GET /api/records/1042
as user: clinic-b-readonly
200 OK · record owned by clinic-a

✓ Validated IDOR, cross-tenant read
✓ Captured request, response, hash

Attack paths over isolated findings

See how the pieces connect.

Three medium findings can add up to one critical route to the data. Aegis maps findings to MITRE ATT&CK techniques and builds the graph, so the report explains the risk the way an attacker would use it.

Remediation follows the same graph: fix the step that breaks the most paths first.

Exposed admin login T1190
Reused service credential T1078
Database reachable internally T1021
Patient records Goal

Vulnerability scanning

Start before the attacker does.

Point Aegis at a repository and it scans the code, the dependencies and the infrastructure files, all on your Mac.

API_KEY = "••••••••••••"
# high entropy · redacted

Secrets detection

Pattern matching and entropy analysis find leaked credentials, API keys and tokens. Reports redact them by default.

package.jsonrequirements.txtGemfile.lockpom.xmlgo.sum

Dependency auditing

Reads common dependency manifests and checks them against the OSV vulnerability database. Only the package name and version are sent.

InjectionWeak cryptoHardcoded secrets

Static analysis

Language-aware patterns for common vulnerability classes, with optional Semgrep or OpenGrep rulesets if you already use them.

TerraformKubernetesDockerfile

Infrastructure as code

Misconfiguration rules for Terraform, Kubernetes YAML and Dockerfiles, with optional Trivy or Grype container image scans.

CycloneDX 1.5SARIF

SBOM and standard outputs

Generate a CycloneDX software bill of materials and export findings as SARIF for the tools your team already runs.

GitHub ActionsGitLab CIAzure DevOps

CI gates

Generate pipeline gate configurations so a build fails when a finding crosses the threshold you set.

Bounded autonomy

It works for you. It asks first.

The operator can plan a sequence of checks and carry it out, which saves hours on a large scope. It cannot leave the scope, and it stops for approval before any step that could affect the target.

  • Scope is enforced by the engine, not left to memory
  • Approval gates on every active or risky action
  • A kill switch stops all activity at once
  • Passive by default. Active testing needs recorded authorization.
  • Every authorization and launch is written to the audit log
Approval required

Run active SQL injection tests?

Target portal.example.test is in scope for this engagement. This step sends test payloads to 6 parameters.

Approve stepSkipStop all

Built for regulated work

Where a breach costs the most.

Sector-aware defaults tune the testing and the report for the organizations that hold the most sensitive records.

✚

Medical

Clinics, labs and health software, where web and API testing protects patient records.

§

Legal

Firms and legal platforms, where client confidentiality depends on access controls that hold.

$

Finance

Financial services and payment systems, where findings have to stand up to an auditor.

One tool, three ways to work

Fits the job you are doing.

Developer

Scan your own repositories for vulnerabilities, leaked secrets and dependency risk. A light workflow with no engagement overhead.

Enterprise

Workspaces and engagements with scope control, authorization, evidence capture, a risk register, retest tracking and audit logging.

Consultant

Authorized assessments for clients, with formal scope, an evidence workflow and client-ready reports.

Tech specs

In development. Features and requirements may change before release.

Availability
In development. Pricing and availability have not been announced.
Platform
macOS, native on Apple Silicon
Network
Quick, standard, full and custom port profiles · service detection · OS fingerprinting
Web and API
Websites, REST and GraphQL · SSRF, XXE, path traversal, open redirect, IDOR, CSRF, XSS, cookie and header checks
SQL injection
12 techniques · 7 database backends · database fingerprinting
Proxy
Intercepting proxy with TLS termination · SSL-strip and certificate-pinning detection
Code scanning
Secrets · dependencies (OSV) · static analysis · Terraform, Kubernetes and Dockerfile rules · CycloneDX SBOM
Optional adapters
Semgrep or OpenGrep, OWASP ZAP, Trivy or Grype, when already installed on your Mac
Analysis
Exploit validation · MITRE ATT&CK mapping · attack graph · risk scoring
Reporting
Markdown, HTML, JSON, SARIF, CycloneDX · redaction on by default · remediation and retest tracking
Safety
Scope enforcement · approval gates · kill switch · audit log
Privacy
Local processing. Credentials in the macOS Keychain. No telemetry. Network traffic only to targets you authorize and to optional vulnerability lookups.

Frequently asked questions

Who is Aegis for?

Penetration testers, internal security teams and developers who want to test systems they own or have written permission to test. It is a professional tool for authorized work.

Can I use it against any website or network?

No. Testing systems without the owner's permission is illegal in most places. Aegis requires you to define scope and record authorization before active testing, and it blocks targets outside that scope.

Does it replace a penetration tester?

No. It does the repetitive work, keeps the evidence straight and shows how findings connect. Judgment about what matters to a particular organization still belongs to a person.

Is it safe to run against production systems?

New targets start in passive mode. Anything active needs explicit approval, and a kill switch stops all activity at once. As with any security testing, agree on timing and scope with the system owner first.

Does my source code or client data leave my Mac?

No. Scanning runs locally. The only outside lookups are optional vulnerability database queries, which send a package name and version, and the connections you authorize to your own targets.

When will it be available?

Aegis is in active development. Email us to follow along or to ask about early access.

Know before they do.

Aegis is in development at Forensic Intelligence.

More from Forensic Intelligence

MITRE ATT&CK is a registered trademark of The MITRE Corporation. OWASP and ZAP are trademarks of their respective owners, as are Semgrep, Trivy, Grype, Terraform, Kubernetes, GitHub, GitLab and Azure DevOps. Aegis is not affiliated with any of them.