How Equalis OpsReg works
The platform reads your Azure configuration through Azure Resource Manager and Azure Resource Graph with read-only roles, evaluates it against versioned rules and stores the results as write-once evidence in EU regions.
Architecture
What runs where, and how data moves: configuration is read from your tenant, read-only, and findings go out only to the tools you connect.
Your Azure tenant
- SubscriptionsFrom 1 to 50, each an audit scope
- Role assignments (read-only)Reader, Security Reader, Cost Management Reader
- Multi-tenant applicationAdmin consent; access revocable on demand from your own tenant
Azure Resource Manager and Azure Resource Graph, read-only
Equalis OpsReg · Azure North Europe, backups in West Europe
- Rule engine437 versioned rules, five frameworks
- Evidence storeWrite-once records, kept for seven years while subscribed
- Dashboards and PDF exportsPer framework, per subscription
Connectors
- Microsoft Teams, Slack, Email, Jira, ServiceNow, PagerDuty, Webhook
Findings are sent to the tools your teams use
Onboarding
Connecting a subscription takes an administrator who can grant admin consent in Microsoft Entra ID and assign roles on the subscription (for example Owner or User Access Administrator). It is designed to take 10 to 15 minutes, up to the end of the first full scan.
Create the account
Sign in with a one-time code sent to a business email address. Personal mailbox providers are refused.
Grant consent
An administrator consents to the multi-tenant application in Microsoft Entra ID. Access is revocable on demand by removing the role assignments and the enterprise application.
Assign roles
A Deploy to Azure template assigns Reader, Security Reader and Cost Management Reader on the chosen subscriptions.
First scan
The first full scan applies all 437 rules across the five frameworks and fills the dashboards.
Evaluation
Each scan reads the connected subscriptions through Azure Resource Graph queries and Azure Resource Manager read APIs, and receives resource metadata: types, properties and tags, diagnostic settings, network rules, encryption state, role assignments and backup configuration, together with the security recommendations and alerts Azure exposes for those resources.
The rule engine compares each relevant property with the value the rule expects. Rules are written by people, versioned and boolean, so the same configuration always produces the same result and the record shows which rule version produced it.
The platform reads configuration and security metadata, never the content of your workloads. The roles grant no access to the data in your databases, storage accounts or virtual machines. The Reader role also allows queries on log data in Log Analytics workspaces in those subscriptions.
- Data sources
- Azure Resource Manager, Azure Resource Graph
- Rules
- 437, versioned
- Results
- Pass, fail, not assessed
- Storage
- Write-once, seven years while subscribed
- Regions
- Azure North Europe; backups in West Europe
Access you grant
Three built-in reader roles, with no write access to your resources, scoped to the subscriptions you choose.
| Role | Why it is needed |
|---|---|
| Reader | Read the configuration of all resources. |
| Security Reader | Read the security recommendations, alerts and security states Azure exposes for your resources. |
| Cost Management Reader | Assigned by the same template for a later capability; the current version reads no cost data. Like the other two roles, it grants no write access to your resources. |
Access is revocable on demand: you can remove the role assignments and delete the enterprise application from your own tenant whenever you decide.
Contact
Demonstrations are run in French or English, in thirty minutes, by the people who build the platform.
The Black Church, St. Mary's Place
Dublin 7, D07 P4AX, Ireland
contact@equalistech.comRequest a demonstration (opens in a new tab)