Our scrubbing & audit layer, running Sigmix-authored firmware — with an optional PCIe card for the appliance.
Explore Sigmix Guard
Results and evidence stay in the workspace inside your environment; the software only ever reads the systems you selected.
See your posturePoint it at systems you select. It maps that environment, connects related findings, and holds anything further until someone in your tenant approves it. You start it. You stop it. The software, hosting, and compute stay with Sigmix.
Inside the console your team gets an overview, connected findings, the environment map, ranked items, and the approvals your tenant signs.
Rule engines and exposure scanners are superb at what they have already seen, and they hand back a list. Sigmix Red builds a working model of the environment your tenant selected and reads it from that model — so related items arrive connected as a path, ranked, instead of as thousands of isolated rows.
Rules, signatures and heuristics — excellent against known techniques, run on a schedule and summarised after the fact.
An AI model of the environment your tenant selected sits at the core — built from what the software reads there, not from a rule list.
Your admin creates the tenant, selects the systems, and activates the job. The software reads that scope, builds a model, and stops at the approval gate. Your team reviews the result in the product. Our staff host and support the software. They do not start jobs or choose systems.
A big organisation accumulates a decade of DNS records, staging sites, acquisitions and abandoned projects. That sprawl — the dangling records, the end-of-life servers nobody owns — is what an inventory never had and a reader never sees. Inside the systems you select, Sigmix Red maps all of it and shows you what is actually reachable.
Every run follows the same controlled cycle. Nothing beyond the read step proceeds without an explicit approval from a person in your tenant, and every action the software takes is written to a tamper-evident audit record.
You select the systems and activate the workspace. The selection is locked; anything outside it is refused, not attempted.
Selected environmentThe software maps only what you selected, building a live model of records, names, services and how they relate — read-only.
It connects related findings and ranks them, by how close each path gets to something you actually care about.
Further checks wait for a person in your tenant. Least-intrusive by default; nothing destructive runs, and no data is copied out.
Tenant approval gateThe result stays in the workspace: what it found, the steps, and the suggested fix — in plain language, routed to the right owner.
When you change the environment, you run it again — so the picture is never stale. When a fix ships, Red re-checks it.
Described by outcome, not method. Inside the systems your tenant selects, the software reads across the layers that matter and relates what it finds.
Finds the internet-facing records and services inside your selection — including the ones nobody remembered — and re-reads them when you run it again.
Reasons about how your apps actually behave — access control, business logic and authentication flaws that signature scanners walk past.
Maps over-privileged roles, stale keys and risky trust relationships, then shows which ones actually open a path — not just a long list.
Severity at a glance, the paths that matter, and a live view of what the software is doing right now — including anything waiting on your approval.
It is hosted software licensed to your organisation. The systems it reads are the ones your admin selects; the job starts when someone in your tenant activates it, and stops when they stop it. Selection, approval and oversight are enforced by the product, not just promised in a contract.
Sigmix Red fits your security posture, not the other way around — a sealed appliance in your own building, an in-Kingdom managed cloud, or governed by Sigmix Guard™. Wherever it runs, your environment, results and evidence stay under your control.
Red runs on a sealed Sigmix appliance inside your data centre. Results stay there.
Results stay in your environmentPrefer managed? Run Red in an in-Kingdom, data-resident environment — same software, Saudi compute.
Resident in the KingdomEvery action is written to an audit record through Sigmix Guard — the same independent enforcement layer that governs the rest of the platform.
Tamper-evident auditA short walkthrough: the software maps a selected environment, connects a path, and holds at the approval gate. Prefer to read? Take the brochure to your team — bilingual, 20 pages.
Open a workspace, or talk to us about deployment.
Hosted software. Sigmix Red is hosted software. The client selects the systems, activates the job, and can stop it. Sigmix hosts and supports the software. Sigmix staff do not select systems and do not start jobs. The software reads only the systems the client's tenant has selected, holds anything beyond the read step for an approval signed inside that tenant, and does not run destructive operations by default. Screens shown on this page are design mockups with illustrative data and do not depict any real customer, environment or finding.