RIG Security
Secretless Isn’t Riskless: Introducing SPIFFE Posture commercialFree plan: not checked yet
The section your link pointed to isn't on RIG Security's page any more, so we've brought you to the top.
Rig Security is an identity protection platform that sees, protects, and enforces every identity for people, non-human identitiesnon-human identitiesA non-human identity, an account or credential used by software or a device rather than a person. Service accounts, workload identities and automation tokens need their own permissions and lifecycle controls., and AI agents.
What you can do now
Summary
RIG Security is a commercial identity-access cyber tool that runs as a server and monitors identity activity, including AI agents and workload credentials. It is aimed at identity-security and ITDRITDRIdentity Threat Detection and Response: a discipline focused on detecting and responding to attacks that abuse identity systems such as Active Directory or IAM platforms, giving cyber tools visibility into credential-based intrusions. teams that need to distinguish a person from an agent using that person’s credentials. Its documentation positions it around identity protection, with capabilities including endpoint policy decisions before requests reach AWS or Kubernetes, process-tree analysis, and executable remediation for Entra IDEntra IDMicrosoft's cloud-based identity and access management service, formerly Azure Active Directory, used by cyber tools to authenticate users and enforce access policies in Microsoft 365 and Azure environments. findings with rollback and verification. Launched in 2024, it has had 12 tracked releases, with the last released nine days ago.
Rig Security is an identity protection platform that sees, protects, and enforces every identity for people, non-human identities, and AI agents.
How RIG Security helps
Which service account or workload belongs to a specific person?
resolves service accounts, workloads, and tokens back to the human owner using a correlation engine that uses name matching across spellings and initials.
Are all the different types of identities (user, service account, token, AI agent) traceable to a single person?
correlates accounts, tokens, and AI agents by tracing them back to a human owner via its correlation engine.
What types of access permissions are currently in place for an identity?
provides a view of an identity's permissions, detailing what it can do, what it can't do, and what roles it holds.
Can an AI agent's actions be differentiated from a person's direct session?
allows security teams to identify and stop only the actions performed by an AI agent that exceed its authorized scope.
What is the overall risk posture based on correlated identity signals?
joins disparate security signals (like unusual logins, role escalations, or credential reuse) into a single story identifying the origin, identity, and target of an attack.
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for RIG Security, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail RIG Security puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What RIG Security connects to, runs on and detects, read from its release notes and docs. So far: 4 new detections, 1 new integration.
5 changes, tracked since Nov 9, 2026.
-
Nov 92026
new SPIFFE Posture checks — AWS
With IAM Roles Anywhere
AWS trust boundaries: trust-anchor pinning, certificate identity conditions, broad SPIFFE wildcards and missing or overly broad OIDC subject restrictions. Roles Anywhere infrastructure: revocation-list configuration, permitted session duration and session naming that preserves certificate attribution.
-
Nov 92026
new SPIFFE Posture checks — issuer and signing-key configuration
With federation configurations
Issuer and signing-key configuration: risky endpoints in supported federation configurations, including insecure schemes, public IP endpoints and temporary tunnel services.
-
Nov 92026
new SPIFFE Posture checks — privileged federation
With Microsoft Entra ID
Privileged federation: SPIFFE credentials that lead into Entra applications with Tier 0 or Tier 1 privileges.
-
Nov 92026
new SPIFFE Posture checks — identity hygiene and shared access
With SPIRE
Identity hygiene and shared access: informational signals that help teams review trust-domain naming and the destinations accepting the same issuer and subject.
-
Nov 92026
new SPIFFE Posture platform integrations
With AWS, Microsoft Entra ID, Azure, Snowflake, Databricks
The release covers AWS, Microsoft Entra ID, Azure, Snowflake and Databricks. It evaluates the configuration collected through Rig's connectors
Identity & access 1
Cloud platforms & services 2
Databases & data platforms 2
Nothing first seen in this window. That doesn't mean RIG Security shipped nothing, only that we found no record of it.
How we count
Read from 1 of 3 release notes and docs updates we hold for RIG Security. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through RIG Security's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
3 entries
No entries match these filters.
- November 20262
- October 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.