IRAP
How to Grant Cybernion Read Only Access in Azure and AWS
22 Sept 2026 · Updated 22 Sept 2026
An assessment needs read only visibility, enough to see how your environment is configured and nothing that can change it or read your data. In Azure, assign Reader, Security Reader, Global Reader and Key Vault Reader. In AWS, attach SecurityAudit, ViewOnlyAccess and read only policies for Security Hub, GuardDuty, Inspector, Access Analyzer, Config and WAF. The only thing we hand over is an email address.
Before an IRAP assessment or other cloud assessment starts we ask for read only access to your cloud environments. The goal is to see how your controls are actually configured, from the platform down, rather than rely on what a diagram or a questionnaire says. The access below is the least that does that job. None of it lets us change anything, and none of it exposes the contents of your data or your secrets.
Our principle: least privilege, read only, time boxed
We ask for the smallest set of roles that lets us complete the work, all of them read only, and we expect the access to be removed when the engagement ends. If a role on this list does not fit how your tenant or accounts are organised, tell us and we will work out the narrowest alternative. We would rather ask twice than hold more access than the job needs.
The only thing we hand over is an email address for the assessor. You create an account for it in your own directory, put it in a read only group, and grant the access to that group rather than to the account. We never ask you for an account, a credential or a key, and you never send us one.
Microsoft Azure: what to set up
Create an account for the email address we provide, then grant it these four built in read only roles.
| Role | What it lets us see |
|---|---|
| Reader | Configuration of all Azure resources: compute, storage, networking, databases, identity and policy |
| Security Reader | Microsoft Defender for Cloud secure score, recommendations and alerts |
| Global Reader | Entra ID configuration, Conditional Access, and the Microsoft 365 admin centres |
| Key Vault Reader | Key Vault settings and metadata, not the secret, key or certificate values |
What to set up
- Create a role assignable security group in Microsoft Entra ID, for example “External assessors”
- Assign the roles to that group, not to the account: Reader and Key Vault Reader at your root management group so they cover every subscription, present and future, and Global Reader and Security Reader as directory roles
- Add our email address to the group, inviting it as a guest first if it is not already in your directory
- Require multi factor authentication on the account
- Sign in is ours to run: we connect with the Azure CLI (
az login) or Azure PowerShell (Connect-AzAccount), both interactive, so no keys or secrets change hands. For a guest account we pass your tenant id - Remove our account from the group when the engagement ends
Reader covers resource configuration, Security Reader is the read only role for Microsoft Defender for Cloud, Global Reader is the read only counterpart to Global Administrator for identity configuration such as Conditional Access, and Key Vault Reader reads how a vault is set up without ever reading what it holds. Read access to Microsoft Intune comes with Global Reader, so no extra role is needed. If Microsoft Sentinel is in scope, add Microsoft Sentinel Reader.
Amazon Web Services: what to set up
Create an identity for the email address we provide, then attach these AWS managed read only policies.
| Policy | What it covers |
|---|---|
| SecurityAudit | Security configuration and logs across services, including IAM, security groups and CloudTrail |
| ViewOnlyAccess | Listing and describing resources across services, so nothing in scope is invisible |
| AWSSecurityHubReadOnlyAccess | Security Hub findings and standards |
| AmazonGuardDutyReadOnlyAccess | GuardDuty findings |
| AmazonInspector2ReadOnlyAccess | Amazon Inspector vulnerability findings for EC2, container images and Lambda |
| IAMAccessAnalyzerReadOnlyAccess | IAM Access Analyzer findings |
| AWSConfigUserAccess | AWS Config rules and resource compliance |
| AWSWAFConsoleReadOnlyAccess | AWS WAF web ACLs and rules, and where they are attached (CloudFront, load balancers, API Gateway) |
What to set up
- In IAM Identity Center, create a permission set and attach the read only policies above to it
- Create a group, for example “External assessors”, and add our email address to it as a user, so it has no long lived access keys
- Assign the group to the accounts in scope with that permission set, which creates the underlying read only role in each account
- Require multi factor authentication
- Sign in is ours to run: we use the console and the AWS CLI or SDKs, signing in with
aws sso loginfor short lived credentials. Do not create or send us long lived access keys - Remove the group assignment, or our account, when the engagement ends
SecurityAudit and ViewOnlyAccess give the base read coverage; the five service policies give us the findings from Security Hub, GuardDuty, Amazon Inspector, IAM Access Analyzer and Config; and AWSWAFConsoleReadOnlyAccess reads your WAF web ACLs and where they are attached. We do not ask for the broader ReadOnlyAccess policy, because it also reads the contents of storage such as S3 objects and DynamoDB tables, and an assessment needs the configuration, not your data. Depending on scope we may ask, per engagement, for a narrow read of specific items such as CloudTrail or CloudWatch log content, AWS Organizations service control policies, or Trusted Advisor security checks, raised one by one rather than held as standing access. If you do not use IAM Identity Center, create a read only IAM role with these policies and a trust policy that lets our account assume it, rather than an IAM user with long lived keys.
What this access deliberately cannot see
Across both clouds, the required roles cannot change a single setting, and cannot read the data your controls protect. In Azure the roles stop at Key Vault metadata and never expose a secret value. In AWS the roles stop at configuration and never read a storage object. If a control review truly needs to confirm the contents of something sensitive, we raise it with you first and agree a narrow, time boxed way to do it, rather than hold that access as standing permission.
Frequently asked questions
Does granting this access let Cybernion change anything in our environment?
No. Every role and policy listed here is read only. We can view configuration, posture and logs to form findings, but we cannot create, modify or delete anything, and we cannot read the contents of your data stores or the values of your secrets.
Can Cybernion read our data or secrets with this access?
No. The Azure roles stop at Key Vault metadata and never expose secret, key or certificate values, and none of the AWS policies grant access to storage contents. This is deliberate: an assessment needs to see how controls are configured, not the data they protect.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Microsoft Entra built-in roles, learn.microsoft.com, 2026
- Azure built-in roles, learn.microsoft.com, 2026
- User roles and permissions, Microsoft Defender for Cloud, learn.microsoft.com, 2026
- Role-based access control with Microsoft Intune, learn.microsoft.com, 2026
- AWS managed policies for job functions, docs.aws.amazon.com, 2026
- AWS managed policies reference, docs.aws.amazon.com, 2026
Last updated: 22 September, 2026
