Skip to content

What Seylo reads in your cloud

A cloud account is read-only, and more than that: it reads metadata only. This page is for whoever reviews the grant before it is made.

Whatever Seylo reads can end up in front of a model during a Nightshift investigation, so Seylo never asks for a value, and Test refuses a grant that holds one of these:

Never Azure AWS Google Cloud
Secret values Key Vault Secrets User, vaults/secrets/getSecret/action secretsmanager:GetSecretValue, and any wildcard that covers it, such as secretsmanager:Get* roles/secretmanager.secretAccessor (secretmanager.versions.access)
Stored data Storage Blob Data Reader, any blob, queue or table data action s3:GetObject (and s3:Get*), dynamodb:GetItem, Query and Scan, sqs:ReceiveMessage Object reads, roles/storage.objectViewer
Keys and settings Storage account listkeys, App Service config/list (app settings and connection strings), Function keys ssm:GetParameter*, kms:Decrypt -

A wrong secret is found without its value. When a credential stops working, Nightshift compares three facts, none of them a secret:

  1. the secret’s version ids and dates in the vault, against the version the pods mounted;
  2. the dependency refusing the credential, in the logs Seylo already reads, such as password authentication failed;
  3. the activity log: who changed the secret, the firewall rule or the role, and when.

One custom role per subscription, Seylo Reader <subscription ID>, which you create from the file the portal gives you, seylo-reader.json:

{
"Name": "Seylo Reader <subscription ID>",
"IsCustom": true,
"Description": "Seylo, read-only: resources, metrics, logs, the activity log, the bill and Key Vault secret names and dates - never a key, token, app setting or secret value. Delete this role to revoke it.",
"Actions": [
"*/read",
"Microsoft.OperationalInsights/workspaces/query/read",
"Microsoft.OperationalInsights/workspaces/query/*/read",
"Microsoft.Insights/components/query/read",
"Microsoft.CostManagement/query/read"
],
"NotActions": [ "... the 31 reads listed below ..." ],
"DataActions": [],
"NotDataActions": [],
"AssignableScopes": ["/subscriptions/<subscription ID>"]
}
  • */read is what Azure’s built-in Reader holds. The four query reads are inside it already; they are named so the role says what Seylo queries: Log Analytics and Application Insights (failures only, during an investigation) and Cost Management (your bill).
  • No data action at all. Key Vault secret names, versions and dates come through Azure Resource Manager, which never returns a secret’s value. This works for vaults on Azure RBAC and on access policies alike.
  • Protected tables stay protected. A Log Analytics workspace with protected tables answers Seylo’s queries with no rows. Seylo does not ask for more to get round it, and Nightshift reports such an answer as “not visible to Seylo”, never as “no errors”.
  • Who can create it: Owner or User Access Administrator on the subscription.

Every read in */read that Microsoft’s resource provider operations pages describe as returning a key, a token, a credential or an app setting:

Area Operation
Log Analytics Microsoft.OperationalInsights/workspaces/sharedKeys/read, Microsoft.OperationalInsights/workspaces/listKeys/read
Application Insights Microsoft.Insights/Components/ApiKeys/Read, Microsoft.Insights/Components/GetToken/Read, Microsoft.Insights/Webtests/GetToken/Read, Microsoft.Insights/generateLiveToken/Read
App Service and Functions microsoft.web/sites/config/appsettings/read, microsoft.web/sites/config/web/appsettings/read, microsoft.web/sites/config/web/connectionstrings/read, microsoft.web/sites/config/snapshots/read, microsoft.web/sites/slots/config/appsettings/read, microsoft.web/sites/slots/config/web/connectionstrings/read, microsoft.web/sites/slots/config/snapshots/read, microsoft.web/sites/publishxml/read, microsoft.web/sites/functions/masterkey/read, microsoft.web/sites/functions/token/read, microsoft.web/sites/hostruntime/functions/keys/read, Microsoft.Web/sites/hostruntime/host/_master/read
Databases Microsoft.DocumentDB/databaseAccounts/readonlykeys/read, Microsoft.Sql/servers/jobAgents/credentials/read
Containers Microsoft.ContainerService/managedClusters/accessProfiles/read (returns a kubeconfig), Microsoft.ContainerService/aiManagers/secrets/read
Networking Microsoft.Network/connections/sharedKey/read, microsoft.network/vpnGateways/vpnConnections/vpnLinkConnections/sharedKeys/read, microsoft.network/vpnGateways/vpnConnections/vpnLinkConnections/sharedKeys/default/read, Microsoft.Network/trafficManagerUserMetricsKeys/read
API Management Microsoft.ApiManagement/service/tenants/keys/read, Microsoft.ApiManagement/service/users/keys/read, Microsoft.ApiManagement/service/namedValues/read, Microsoft.ApiManagement/service/workspaces/namedValues/read
Automation Microsoft.Automation/automationAccounts/credentials/read

Your inventory, your bill and Nightshift still work under the role: none of the reads they make is in this list.

The seylo-read-only stack gives the role SeyloReadOnly:

Policy What it holds
ViewOnlyAccess (AWS-managed) List and describe, across services. Metrics (cloudwatch:Get*, List*), RDS, EC2, VPC, load balancers, Route 53, CloudFront lists and CloudTrail event history are all in it
seylo-read-this-role Read this one role (its tag and policies), the account alias, and lambda:GetAccountSettings, the account’s Lambda count per region
seylo-deny-values Deny ec2:DescribeInstanceAttribute, lambda:ListFunctions, lambda:ListVersionsByFunction and bedrock-mantle:CallWithBearerToken
seylo-read-costs ce:GetCostAndUsage only: your bill, for prices
seylo-quota-read servicequotas:GetServiceQuota and servicequotas:ListServiceQuotas: your vCPU quota numbers, so Savings never proposes a size the account cannot start. ViewOnlyAccess holds no Service Quotas action. A stack saved before 10 November 2026 does not have it: save the new template, deploy it, and press Test
seylo-nightshift-investigate Only with the Nightshift box ticked: logs:StartQuery, logs:GetQueryResults, logs:StopQuery, secretsmanager:ListSecrets, secretsmanager:DescribeSecret, secretsmanager:ListSecretVersionIds, cloudwatch:DescribeAlarms

Why the Deny. ViewOnlyAccess lets a role read two things that are values, not metadata: ec2:DescribeInstanceAttribute returns an instance’s user data, and lambda:ListFunctions and ListVersionsByFunction return every function’s environment variables. The Deny takes them away on every stack, ticked or not, so Seylo counts Lambda functions with lambda:GetAccountSettings instead, which carries no configuration. bedrock-mantle:CallWithBearerToken is denied because its name says invocation, not read; Seylo never needs it.

secretsmanager:DescribeSecret returns a secret’s details, version ids and last change date, not its value.

Role Why
roles/viewer Resources and their settings, logs (it includes Logs Viewer), metrics, and Admin Activity audit logs
roles/cloudasset.viewer The resource inventory
roles/secretmanager.viewer Only with the Nightshift box ticked: secret names and versions. It holds no secretmanager.versions.access, the permission that reads a payload

Seylo does not ask for roles/logging.privateLogViewer, so Data Access audit logs, which record who read which data, are not read.

Test judges the grant from the roles Seylo reads back from your cloud, never from what the steps asked for:

  • Read means read. An Azure role with any action that is not a /read, or any data action; an AWS policy outside ViewOnlyAccess and SecurityAudit, or an inline action that is not a metadata read; a Google Cloud role outside the viewer list. Each is refused, by name.
  • Metadata only. Whether the grant could read a key, token or setting Seylo never uses. It informs and never fails the connection. See test before save.