The Atlas take.
Astrix agent and non-human identity capabilities remain useful research context, but this is explicitly transition coverage. The official site states standalone new-license sales ended June 30, 2026, while existing customers continue under their agreements and capabilities move into Cisco over time. Atlas would prioritize current support, inventory continuity and a documented migration path rather than recommend buying the historical standalone offering. The underlying identity work remains important: discover owners and permissions, constrain credentials and prove lifecycle changes. Future Cisco integration must be verified as an actual available product and contract.
02 / DEFINE THE BOUNDARY
What you are actually evaluating.
This is transition coverage for Astrix capabilities and existing customers. Astrix states that standalone new-license sales ended June 30, 2026.
This profile documents Astrix’s identity-security capabilities for existing customers and evaluates their transition into Cisco. It should not be treated as a currently orderable standalone offer for new customers. The technical focus is governed credential provisioning and lifecycle, with commercial and migration status established separately.
- Also covers
- Agent discovery and security posture
- Deployment surface
- SaaS agents · Custom/cloud agents
- Integration point
- Platform connector · Identity provider
- Availability
- Legacy / acquired
Standalone new-license sales ended June 30, 2026. This label records the acquisition transition, not end of existing service.
Names you may encounter Astrix Security. Historical names do not establish current feature equivalence.
03 / THE CONTROL PATH
Where it sits. How it works.
Atlas architecture interpretation: supported connectors discover agent-associated identities and access; selected control-plane functions provision or govern credentials; lifecycle changes need verification at each target during transition.
- 01
Connected agents, MCP and NHIs
Record the supported environment, identity owner and current permission inventory.
- 02
Identity posture and control plane
Review risky access and the currently entitled provisioning or credential-policy functions.
- 03
Target lifecycle and transition evidence
Verify remediation, export continuity and a supported path for the existing customer deployment.
Standalone sales ended June 30
The current notice says new standalone-license sales ended June 30, 2026. Existing customers continue service and support under their agreements while Astrix works to bring capabilities into Cisco.
Policy before onboarding
The documented flow defines policies, selects a permission profile during agent deployment, and then manages the agent through ACP inventory. Confirm the integration method with the developer’s chosen agent framework.
Verify Cisco migration scope
The transition notice describes integration into Cisco over time without establishing feature-for-feature equivalence in a specific Cisco product. Obtain a dated migration plan, available SKU, integration ownership, and support obligations.
04 / WHAT EARNS ITS PLACE
Strengths, with the evidence attached.
Atlas analysis of documented capabilities; availability and behavior depend on the edition and environment.
Identity lifecycle is a defined purpose
The Agent Control Plane material describes scoped and short-lived access concepts, giving existing customers concrete controls to validate.
Discovery has a separate surface
The discovery page describes agent/NHI inventory context that can be reconciled against current connected systems.
Inspect the documented capability notes
Evidence reviewed: Astrix’s current Cisco transition notice and Agent Control Plane product description.
Agent and non-human identity inventory
Astrix describes discovery of agents, MCP servers, and NHIs with risk and business-use context. Its security layer identifies excessive privileges, vulnerable configuration, abnormal activity, and policy violations.
Pre-approved permission profiles
ACP describes administrators defining granular use-case policies and developers selecting a pre-approved profile when onboarding an agent. The agent appears in inventory with the associated policy.
Short-lived and just-in-time credentials
The ACP page describes precisely scoped, short-lived credentials and context such as IPs, tags, and teams. Validate the supported credential issuer and target resource rather than assuming all tokens have identical semantics.
Ownership and lifecycle evidence
ACP describes ownership, attestation, audit trails, and onboarding shadow agents into governed access. These functions are intended to keep identity context attached as agents are created and retired.
05 / KNOW THE COMPROMISES
The tradeoffs to take seriously.
Architectural implications and procurement questions from Atlas; these are not independently measured product failures.
Standalone new sales have ended
The official transition notice sets June 30, 2026 as the end of new standalone licenses; current procurement must be checked with Cisco.
Future integration is not current entitlement
The site describes bringing capabilities into Cisco over time; do not infer delivery, packaging or migration terms from that intent.
Additional coverage boundaries
- An Astrix capability page is evidence of the documented design, not proof that the same feature is generally available in a Cisco module today.
- Short-lived credentials reduce exposure duration but do not decide whether every permitted action matches the user’s intent. Resource and task restrictions still need evaluation.
- For existing deployments, confirm connector continuity, credential issuers, data handling, policy export, contract renewal, migration timing, and behavior of active sessions during retirement.
06 / FROM PURCHASE TO PRACTICE
Make it work in your environment.
A proposed implementation sequence. Confirm supported versions, permissions, and rollback with the current documentation.
- 01
Confirm the existing agreement
Record support contacts, entitled functions, current renewal terms and any documented transition commitments.
- 02
Preserve operational continuity
Verify inventory, configuration and audit export and identify connector dependencies before any migration.
- 03
Revalidate identity lifecycle
Use a disposable agent to test scoped credentials, approved permission cleanup and target-side loss of access.
07 / THE OPERATING COMMITMENT
The bill is only part of the cost.
Commercial shape
For existing customers, compare renewal/support and any proposed Cisco transition against the current contract. New buyers need an available Cisco product and written capability map rather than a historical Astrix quote.
- Existing agreement and support/renewal terms
- Current Cisco packaging and transition requirements
- Connector continuity, exports and lifecycle operations
08 / COMPARE THE JOB
Put these beside it.
Alternatives worth examining for the same problem. Check each offering’s scope before treating it as a substitute.
Oasis Agent Identity Security
Compare currently available discovery and remediation of agent-associated NHIs on the required connected systems.
OktaOkta for AI Agents
Compare a managed agent-identity/resource model when the organization can adopt supported Okta connections.
09 / MAKE THE DECISION OBSERVABLE
Earn confidence through a real evaluation.
Suggested by Atlas. Agree acceptance criteria, use synthetic fixtures in an authorized environment, and capture both useful work and failed controls.
- TEST 01
Reconcile a known agent/NHI roster
Acceptance evidence: Keep ownership, permissions and missing-coverage evidence.
- TEST 02
Exercise one currently supported scoped credential lifecycle
Acceptance evidence: Verify target access before and after expiry/revocation.
- TEST 03
Export an existing-customer inventory and audit sample
Acceptance evidence: Document usable identifiers, support responsibilities and transition gaps.
START WITH ONE EXERCISE
An existing-customer test agent retains a service credential after its workflow is retired.
Evidence to look for: Verify credential removal and denied access while preserving the product-transition context.
Questions to bring to the vendor
- Which licenses remain available to new customers?
- Which capabilities have moved into a Cisco offering?
- How are existing integrations supported during transition?
10 / SHOW THE WORK
Evidence, and what is still unknown.
What this research cannot establish
- Atlas has not independently tested identity discovery or credential enforcement.
- Confirm current Cisco availability, existing-customer support and any migration commitments in writing.
Dossier research reviewed October 18, 2026. Earlier profile references are retained for traceability; products and commercial terms change.
- Astrix: Cisco acquisition and standalone-sales notice ↗Lifecycle
- Astrix: Agent Control Plane provisioning model ↗Product information
- Astrix agent discovery and visibility ↗Product information
KEEP BUILDING YOUR JUDGMENT