Identity categories
Workforce · External and third-party · Non-human · AI agents
Adaptive Identity Security and Governance
Understand who has access, how they received it, and whether it remains appropriate
Connect identity, entitlement, access-path, ownership, and available usage information to support least-privilege decisions and accountable remediation.
MTX Identity Security & Governance helps security and identity teams examine access across connected SaaS, cloud, on-premises, and custom applications. It provides context for access reviews, posture findings, incident investigations, and remediation workflows covering human, non-human, external, and AI identities.
Illustrative identity-security viewFictional sample
9Connected identities
3Human identities
3Non-human identities
3AI identities
6Applications / resources
12Access relationships
4Dormant / unused signals
6Review queue items
3Remediation statuses tracked
ScopedVisibility limited to connected systems
Platform scope
A scoped operating model for identity security and governance
These figures describe platform scope for the prototype, not customer outcomes. Visibility depends on connected systems and available data.
Operating stages
Connect · Understand · Assess · Review · Remediate · Verify
Access-context dimensions
Identity · Resource · Access path · Usage · Business context
Connected access graph
Relationships drawn from systems brought into scope
Identity-security challenges
Common access problems teams need to examine
Select a challenge to see affected roles, evidence, required context, product capability, and a suggested measure.
Fragmented access information
Challenge: Identity and entitlement information may be spread across directories, cloud platforms, SaaS applications, groups, roles and custom systems.
Response: Normalize available access relationships into a connected identity graph.
- Affected roles
- IAM leaders, Security architects, Application owners
- Evidence available
- Connected-system entitlements; Group memberships; Role assignments
- Additional context required
- Systems not yet connected; Custom entitlement models awaiting mapping
- Product capability
- Identity graph normalization across connected sources
- Suggested measure
- Share of priority systems represented in the access graph
Identity operating lifecycle
Six stages from connection through verification
Selecting a stage updates the adjacent interface with the activities and artifacts typical of that stage.
Stage 1 of 6
Connect
Bring selected identity and resource systems into scope through available connectors and permissions.
- Identity providers
- Directories
- SaaS applications
- Cloud platforms
- On-premises applications
- Custom applications
- HR systems
- PAM
- IGA
- Data platforms
Coverage and actions remain limited to connected systems, available data, connector capability, and authorized workflows.
Interactive identity graph
See how identities reach resources across connected systems
Fictional identities and resources illustrate direct, inherited, external, service-account, agent-tool, dormant, and privileged paths. Visibility is limited to connected sample relationships.
Illustrative identity access graphFictional sample
Nodes represent fictional human, non-human, and AI identities on the left and resources on the right. Lines represent access relationships. Select a line or use the table alternative below.
Solid lines: direct, role, service, or privileged paths. Dashed lines: inherited or external sharing. Amber/red emphasize dormant, unused, or higher-priority review signals — not confirmed incidents.
Relationship detail
Illustrative product data- Identity
- Maya Chen
- Resource
- Analytics Platform
- How access was granted
- Direct assignment → Analytics Contributor
- Permission
- Contributor
- Last observed use
- 2 days ago
- Usage frequency
- Weekly
- Resource owner
- Analytics Leads
- Identity owner
- Jordan Hale
- Recommendation
- Keep — recent observed use aligns with role
- Review status
- Not-Started
- Remediation option
- No action suggested
Access relationships corresponding to the identity graph
| Identity | Resource | Path type | Permission | Usage | Review | Priority |
|---|---|---|---|---|---|---|
| Analytics Platform | Direct | Contributor | Active | Not-Started | Low | |
| Cloud Storage | Group-Inherited | Read | Dormant | Reduce | Medium | |
| Constituent Records | Group-Inherited | Read PII fields | Active | In-Review | High | |
| Analytics Platform | External-Sharing | Viewer | Dormant | Not-Started | Medium | |
| Finance Workspace | Role-Based | Admin | Active | Keep | Low | |
| Administrative Console | Privileged | Identity admin (limited) | Unused | Reduce | High | |
| Cloud Storage | Service-Account | Read/Write objects | Active | Keep | Low | |
| Finance Workspace | Service-Account | Export reports | Active | In-Review | High | |
| Source Repository | Role-Based | Deploy | Active | Keep | Medium | |
| Constituent Records | Agent-Tool | Retrieve documents | Active | Reduce | High | |
| Cloud Storage | Agent-Tool | Search indexed content | Active | Keep | Medium | |
| Administrative Console | Privileged | Read ticket admin metadata | Unused | Not-Started | Critical |
Who-has-access explorer
Ask focused access questions against illustrative relationships
Prebuilt questions return fictional results with evidence and context. This prototype does not connect to a live natural-language model or identity systems.
Who has access to this resource?
Illustrative product dataFocus: Finance Workspace
Elena Ruiz — Role-based Admin
Evidence: Finance Manager role → Workspace Admin
Context: Daily observed use
Reporting Automation — Service-account export
Evidence: Service role → Export reports
Context: Owner unconfirmed
Access risk explorer
Investigate posture findings with evidence and unknowns
Findings highlight conditions that may require review. They do not automatically represent confirmed security incidents.
Unused privileged access
Illustrative product dataA privileged permission has no observed use during the selected review period.
- Observation
- Elena Ruiz holds limited identity-admin permission on Administrative Console.
- Supporting evidence
- Permission provisioned; No observed use in 90 days; Role: Finance Manager
- What remains unknown
- Whether break-glass procedures rely on this grant; Seasonal finance-close needs
- Potential impact
- Privileged standing access may exceed current need if unused.
- Suggested reviewer
- Identity Operations + Finance manager
- Recommended action
- Reduce privilege or document exception after authorized review
- Decision status
- New
Usage-aware access review
Decide with business and usage context
Usage is decision context and does not independently determine whether access remains necessary. Recommendations help an authorized reviewer; they do not establish that access should be removed.
Review package
- Identity
- Maya Chen
- Role
- Program Analyst
- Manager
- Jordan Hale
- Resource
- Cloud Storage
- Permission
- Read
- Access path
- Group: Program Analysts → Nested: Storage Readers
- Last observed use
- 45 days ago
- Usage frequency
- Rare
- Peer comparison
- Most peer analysts show monthly or greater observed use
- Resource sensitivity
- Sensitive
- Recommendation
- Review — limited observed use; confirm business need before keeping
Reviewer decision
Lack of observed use does not automatically prove that access is unnecessary.
Human, non-human and AI identities
Govern modern identity categories with ownership and lifecycle context
Discoverability depends on required connectors and available source data. Examples below are fictional.
Human identities
- Employees
- Contractors
- Partners
- Guests
- Administrators
- Managers
Maya Chen
- Owner
- Jordan Hale
- Purpose
- Program analysis
- Resources
- Analytics Platform, Cloud Storage
- Permissions
- Contributor, Read
- Credentials
- Workforce IdP
- Usage
- Mixed active / dormant
- Review status
- In review
- Lifecycle
- Active employee
- Related findings
- Nested group access
Elena Ruiz
- Owner
- Priya Natarajan
- Purpose
- Finance operations
- Resources
- Finance Workspace, Administrative Console
- Permissions
- Admin, Limited identity admin
- Credentials
- Workforce IdP
- Usage
- Active on finance; unused on admin console
- Review status
- Privileged review queued
- Lifecycle
- Active employee
- Related findings
- Unused privileged access
Adaptive and time-boxed access
Move toward access that reflects current need
Illustrative access-request experience. Time-boxed access availability depends on connected systems and licensed product capabilities.
Access request (illustrative)
- Requester
- Maya Chen
- Requested resource
- Finance Workspace
- Requested permission
- Read finance dashboards
- Business purpose
- Quarterly program-cost analysis requested by Finance
- Requested duration
- 30 days
- Current access
- No direct Finance Workspace access
- Peer context
- Two peer analysts hold time-limited read access this quarter
- Resource owner
- Elena Ruiz
- Approval route
- Resource owner → Finance manager
- Expiration
- Requested end date + automated reminder (if supported)
Availability depends on connected systems and licensed product capabilities.
Possible outcomes
Identity incident investigation
Trace unexpected activity through access context
Scenario: a dormant contractor account becomes active and accesses a sensitive resource through inherited group membership. Response options depend on integrations, permissions and organizational policy.
Identity posture and remediation can reduce exposure and support incident response. This prototype does not claim that the platform independently stops lateral movement or prevents a breach.
Step 1: Identity activity observed
Dormant contractor account shows new sign-in and resource access.
Remediation control center
Coordinate approved remediation with an audit trail
Revoking or changing access depends on connector capability, permissions, workflow configuration, and the authoritative source. No real access changes occur in this prototype.
Remediation workspace items
| Finding | Identity | Resource | Priority | Owner | Status | Action |
|---|---|---|---|---|---|---|
| Elena Ruiz | Administrative Console | High | Identity Operations | Reviewing | ||
| Reporting Automation | Finance Workspace | High | Elena Ruiz | Approved | ||
| Service Desk Agent | Administrative Console | Critical | Chris Alvarez | New |
Selected remediation
Illustrative product data
- Finding
- Unused privileged access
- Recommended action
- Reduce privileged permission
- Approval requirement
- IAM change approval
- Connector
- Directory / admin connector (illustrative)
- Verification
- Pending
- Exception
- None
- Last update
- Illustrative — today
Audit trail
- Today · 09:12Finding opened
- Today · 09:40Assigned to Identity Operations
- Today · 11:05Awaiting reviewer decision
Integration architecture
Complement existing identity and security systems
Focus: Oleria technology layer
MTX Identity Security & Governance is positioned as an identity intelligence, posture, governance, and remediation layer. It does not replace directories, IAM, IGA, PAM, HR, cloud platforms, or security operations systems.
Role-based experiences
Tailor the workspace to decision-makers and operators
Select a role to preview the panels that role typically needs. Content remains illustrative.
Illustrative product data
CISO workspace
- Identity posture
Illustrative panel for CISO workflows.
- Privileged exposure
Illustrative panel for CISO workflows.
- External access
Illustrative panel for CISO workflows.
- Non-human identity risk
Illustrative panel for CISO workflows.
- AI identity risk
Illustrative panel for CISO workflows.
- Remediation progress
Illustrative panel for CISO workflows.
Analytics and recommended measures
Illustrative posture, governance and remediation measures
Every figure below is illustrative product data. Values are fictional and are not MTX, Oleria, or customer results.
Illustrative product data
Identity inventory
- Human : 1280
- External : 146
- Non-human : 392
- AI : 28
- No confirmed owner : 41
Illustrative product data
Access posture
210Privileged
164Unused
97Dormant
53External sharing
38Auth gaps
121Excessive
- Privileged : 210
- Unused : 164
- Dormant : 97
- External sharing : 53
- Auth gaps : 38
- Excessive : 121
Chart values are also listed by category labels above the bars.
Illustrative product data
Governance
- In progress : 64
- Overdue : 18
- Decisions : 240
- Delegated : 27
- Exceptions : 14
- Expiring : 22
Illustrative product data
Remediation
- Approved : 45
- Completed : 38
- Verification pending : 12
- Connector failures : 3
- Reopened : 5
- Avg age (days) : 9
Illustrative product data
Platform coverage
Connected systems
24 illustrative
Connector health
21 healthy / 3 attention
Resources represented
186 illustrative
Identity coverage
Scoped to connected systems
Usage-data availability
Partial by source
Data-processing status
Incremental sync simulated
Governance and auditability
Keep ownership, decisions, remediation and evidence accountable
This section describes governance constructs supported by the offering model. It does not claim that the platform establishes legal or regulatory compliance.
Identity ownership
- Employee manager
- Service-account owner
- Application owner
- Resource owner
- AI-agent owner
- Review responsibility
Adoption roadmap
A practical path from scope to improved governance
Phases are sequential planning aids. Fixed implementation durations are intentionally omitted because timelines depend on scope, connectors, and organizational readiness.
Phase 1: Establish scope
- Identify priority systems
- Define identity categories
- Select risk questions
- Establish ownership
- Agree on measures
Offering model
Technology plus MTX services
Oleria identity-security technology
- Identity and access graph
- Usage-aware access context
- Identity-security posture
- Governance workflows
- Investigation support
- Remediation controls
- Reporting
MTX did not develop Oleria’s underlying platform.
MTX implementation services
- Identity discovery
- Architecture
- Connector configuration
- Data validation
- Governance design
- Access-review configuration
- Remediation workflow
- Testing
- Training
- Deployment
MTX managed services
- Connector monitoring
- Posture review
- Access-review support
- Finding triage
- Remediation coordination
- Reporting
- Governance administration
- Service reviews
Evidence discipline
Product maturity and operating evidence
| Capability | Status |
|---|---|
| Identity and access graph for connected systems | Available |
| Usage context where source telemetry is connected | Configured per deployment |
| Access reviews with recommendations | Available |
| Remediation actions via connectors | Configured per deployment |
| AI-agent identity governance views | Early access |
| Time-boxed / just-in-time access patterns | Configured per deployment |
| Adaptive inline enforcement at every application | Planned |
| Managed operations support model | Configured per deployment |
Why MTX Identity Security & Governance
Restrained differentiators for buyer conversations
The offering helps organizations understand access, support least-privilege decisions, and coordinate remediation across connected systems.
Connected access context
Bring identity, entitlement, access path, ownership and available usage information into a shared view.
Governance informed by use
Give reviewers additional context when deciding whether access remains appropriate.
Coverage for modern identities
Support human, external, non-human and AI identity governance across connected systems.
Implementation and operating support
Use MTX services to plan integrations, configure governance, support deployment and establish ongoing processes.
Build a clearer, more accountable view of enterprise access.
Explore how MTX Identity Security & Governance can help your organization understand access relationships, improve reviews, and coordinate remediation across connected systems.