Corporate identity
Signing in to Myrmex follows your company's identity.
- SSO with your identity provider
- ABAC on top of role-based permissions
Myrmex Enterprise
Your operation grows. Control grows with it.
Give your team the capacity to investigate, act and document with AI. With corporate identity, contextual access and integrations that reach your company's systems.
Delegate the work. Keep decisions visible.
Myrmex capabilities, with the governance your company needs.
Enterprise extends the workspace with identity controls, contextual policies and features to connect and organize more complex operations.
The starting point is already a connected operation.
AI agents, integrations, endpoints, alerts, contexts, automation and role-based access are part of the Workspace foundation.
Explore the productOperational governance
Track your environment's exposure and the actions your team takes.
- Security posture management
- Audit logs of actions in Myrmex
Your whole environment
Include internal systems and organize operations across companies or business units.
- Custom integrations with your own systems
- Managed sub-organizations for MSSPs
Continuity for your team
Turn procedures into reusable routines, with support for operations.
- Unlimited playbooks in Enterprise
- Premium support by phone and email
Who can act? In which environment? Under what conditions?
SSO, RBAC and ABAC answer different questions. Together, they identify the person, define their authority and evaluate the context of each access request.
SSO: the identity your company already knows
Federate access with your corporate identity provider. Authentication identifies the person; roles and policies define the scope of access in Myrmex.
RBAC: each role's responsibility
Define permissions for reading, execution and administration. Associate roles with asset groups and assign scopes to service identities used by integrations and automation.
ABAC: the conditions for using that access
Add rules for source IP, time, days and MFA status. Target policies to specific permissions, roles, devices or integrations.
Interactive access policy example
A person attempts to execute an operation in production.
This example requires execution permission, the corporate network and verified MFA. Select a scenario.
- Assigned role
- Operator with execution
- Access source
- Corporate network
- Additional authentication
- MFA verified
SSOVerified
RBACVerified
ABACVerified
Access to the operation allowed
The role permits the operation and the policy's conditions have been met.
Explanatory diagram; no actions are executed. Allowed access does not replace change approvals or extend the connector's technical permissions.
Available ABAC conditionsSource IPTime of dayDay of weekMFA statusDevice typeUser agent
Multiple units. The right context for each task.
Organizations, sub-organizations and contexts help separate environments and responsibilities. Define members, integrations and access rules before expanding operations.
Your organization
Business units
IT environments
Managed clients
Illustrative model for organizing work. The structure follows configured scopes and access.
Organizations and managed environments
In this demonstration, the team navigates organizations and their contexts to work in the selected environment. Roles and policies define access to resources.
Illustrative screens with demonstration data. Features and actions depend on configuration, integrations and granted permissions.
Your company's most important software may have been built by you.
Enterprise supports custom integrations with internal and proprietary systems. Bring your team's ERP, service portal or the application that runs your operations into the AI workspace's context.
Your system. Your process. An integration designed for it.
Software that belongs to your company
Your own systems
Internal applications, APIs and services developed for your business.
Custom integration
Authentication, accessible data and operations defined for your use case.
Work in Myrmex
Queries, investigation and authorized actions with the system's context.
Possibilities to design with your team
“Investigate why this batch stopped processing.”
- What to query
- Query the batch status and the records the API makes available.
- What could become an action
- Consider reprocessing only if the system offers that operation and the identity is authorized.
From a possibility to a connector your team can operate.
Together, we define available interfaces, authentication, read and write limits, validation and maintenance. The delivery scope and connector terms are agreed as part of the project.
Evaluate a custom integrationA production change needs more than a good AI answer.
Bring justification, plan, risk and rollback into the same decision. Configure who proposes, who approves and who administers each context's change rules.
Reviewable proposal
The team inspects what will change and why.
Defined approvers
Rules determine responsible people and the minimum approvals.
Tracked execution
The change follows the workflow and window applicable to its type.
Recorded result
History preserves decisions and outcomes, including partial failures.
Change plan and approval
Separation of duties depends on role and rule configuration. Approval does not grant the integration a permission it does not have.
Connect operations to the architecture you already have.
Start with the sources that answer your team's questions. The agent works on hosts; Collector mode reaches equipment and services through their protocols and APIs.
In your environment
Agent on endpoints
Collects information and performs local actions within the authorized configuration.
Collector and integrations
Connects networks, cloud, tools and internal APIs using the integration's credentials.
Encrypted outbound connection
Myrmex
Context, investigation, proposed action and work tracking.
Identity, permissions and policiesReview connectivity, required data and each integration's permissions during the technical evaluation. Capabilities vary by connector and environment.
Review connection requirementsLeaders need to see what changed. Teams need to explain it.
Audit logs record user actions in Myrmex. Change history, reports and documentation help reconstruct decisions, review outcomes and guide the next task.
User actions in Myrmex
Change decisions and outcomes
Operational reports and documentation
From technical work to the service report
Illustrative report for a managed environment. Evidence supports the assessment of controls; it does not represent certification of the organization.
The same evaluation, through the eyes of each decision-maker.
How do we justify expanding IT capacity?
Connect delegated work to an observable outcome.
Choose a routine that consumes team time. Compare investigation effort, handoffs and delivery quality before and during the evaluation.
What to observe in the pilotTime spent on the routine and work that still requires intervention.
When a fix must wait, the decision stays on record.
An exception needs context. Myrmex lets you justify findings and set an expiry; when the workflow requires risk acceptance, the letter is sent for signature and its status can be tracked.
Follow your environment over time.
Coverage, outstanding controls and posture trends help you choose the next area of work. The executive view stays linked to the findings behind it.
Start with an operation you can evaluate.
Enterprise adoption involves those who operate, design the architecture and own the risks. Define the first scenario and agree on what must be demonstrated before expanding.
- 1
Define the scope
Choose the routine, environments, sources and owners. Establish evaluation metrics and restrictions.
Agreed scenario and success criteria - 2
Validate with the team
Check SSO, roles and policies. Start with queries and add bounded actions, verifying outcomes and blocks.
Technical evidence and reviewed controls - 3
Expand with clear criteria
Add environments and playbooks based on what has been validated. Define continuity, support and the next connectors.
Defined adoption and operations plan
Premium support by phone and email.
Enterprise includes priority assistance. Agree with our team on deployment, channels and terms suited to your operation.
Bring your company's requirements.
Availability, response times, data handling and retention, and commercial terms are part of the evaluation. These requirements should be included in the agreed scope.
Explore Myrmex securityQuestions that belong in an Enterprise decision.
Does SSO replace RBAC and ABAC?
No. SSO provides authentication with your corporate identity. RBAC defines permissions and scope; ABAC adds conditions to access. Authentication alone does not grant permission to execute an action.
Can we integrate software built within our company?
Yes. Custom integrations with your own systems are part of Enterprise. We assess available interfaces, authentication and operations with your team to define the connector and its validation.
What is the difference between audit logs and reports?
Logs record user actions performed through Myrmex. Reports organize findings and outcomes for analysis and communication. Change history adds the decisions and results of the execution workflow.
Can we start without enabling writes to our systems?
The initial scope can focus on queries, using read-only credentials and permissions where the connector supports them. Write actions are evaluated separately, with the necessary technical controls and approvals.
How do we evaluate SSO, support and data requirements?
Bring your company's identity provider, security requirements and support criteria. The evaluation confirms compatibility and defines deployment, support and data handling terms for your scenario.
Bring your environment. Let's design adoption with the people responsible for it.
A conversation about your systems, your controls and the operation you want to improve.