nano SIEM
Integrations

Pull permissions

Supported in:Self-hosted

Compare exact identity grants and resource scopes for cloud pull sources and SaaS pull feeds

Grant access to the resources each pull connector reads. Use the matrix to choose an identity and limit its reach before following the linked setup guide. Every identity here is one you own: a credential stored in nano, or the deployment's ambient cloud identity.

Permissions matrix

Pull typeIdentity modelExact permissions or scopesLeast-privilege resource scopeAccess the connector does not need
AWS S3 via SQSAWS access key, or the deployment's ambient identity (instance profile, IRSA, task role); either can assume a rolesqs:ReceiveMessage, sqs:DeleteMessage, sqs:ChangeMessageVisibility, sqs:GetQueueAttributes; s3:GetObject; kms:Decrypt for SSE-KMSOne queue ARN; arn:aws:s3:::BUCKET/PREFIX*; relevant KMS keys with regional S3/SQS kms:ViaService conditionsNo object writes, bucket listing, queue publishing, or IAM administration. Queue acknowledgments delete messages.
AWS SQSSame as S3 via SQSsqs:ReceiveMessage, sqs:DeleteMessage, sqs:ChangeMessageVisibility, sqs:GetQueueAttributes; kms:Decrypt for SSE-KMSOne queue ARN; relevant KMS key with regional SQS kms:ViaServiceNo S3 access, queue publishing, or IAM administration. Collection changes visibility and deletes acknowledged messages.
CrowdStrike FDRThe FDR access key CrowdStrike issues (stored as an AWS credential); optionally a role to assumeGranted by CrowdStrike: sqs:ReceiveMessage, sqs:DeleteMessage, sqs:ChangeMessageVisibility on the feed queue and s3:GetObject on the feed bucket. sqs:GetQueueAttributes is optional (queue-depth metric only)The feed's queue and bucket (owned by CrowdStrike)Nothing in your own AWS account. Collection changes visibility and deletes acknowledged messages.
GCP Pub/SubService-account JSON key, or Application Default Credentials (Workload Identity)roles/pubsub.subscriber; required consume permission is pubsub.subscriptions.consume (also covers acknowledgment)The specific subscription, not the project or topicNo topic publishing or project administration.
Azure Event HubsEntra app client secret, SAS connection strings, or managed identityAzure Event Hubs Data Receiver; Storage Blob Data Contributor (or a SAS policy with Listen and the storage connection string)Receiver on one event hub; Contributor on one checkpoint containerNo event publishing, Graph API permission, or subscription-wide management role. Checkpoint ownership/blob writes are required.
KafkaConfigured SASL identity and TLS, or your cluster's configured authenticationRead on topics and consumer group; Describe access (implied by Read with Kafka's standard authorizer)Named topics and one consumer-group IDNo Write, Create, Delete, or Alter ACL.
Google Workspace auditService-account key with domain-wide delegationhttps://www.googleapis.com/auth/admin.reports.audit.readonly; impersonated active Workspace super-adminDelegation authorized for this service account's numeric client ID in your Workspace; select only required audit applicationsNo directory-write or Reports write scope. The readonly OAuth scope constrains the impersonated admin's API access.
Okta System LogSSWS API token created by a Read-only AdministratorCreator's Read-only Administrator role; no OAuth scope in this SSWS connectorCustomer org; token inherits creator's role rather than endpoint-specific OAuth grantsNo write administrator role or user/group mutation.
NetskopeREST API v2 token (API_TOKEN)Read grant on each enabled /api/v2/events/dataexport/events/STREAM endpoint; see stream names belowYour .goskope.com tenant and enabled export endpointsNo configuration/admin write grant. The iterator read operation advances server-side read position.
Slack access logsUser OAuth token (USER_TOKEN, xoxp-)admin user-token scopeWorkspace token; TEAM_ID selects a workspace for an org-level token but does not narrow the token grantNo message-posting scope is requested. Exception: admin is broad; do not treat the token as read-only.
Okta users and groups (identity feed okta_users)SSWS API token created by a Read-only AdministratorCreator's Read-only Administrator roleCustomer orgNo user, group or role writes. Syncs nano's user directory; no log source.
Entra directory (identity feed entra_directory)Entra app registration with a client secret (client credentials)Microsoft Graph application permissions to read users and group and directory-role memberships, requested as https://graph.microsoft.com/.default; admin consent requiredYour directory and its registered appNo directory writes. Syncs nano's user directory; no log source.

For Netskope, STREAM is one of alert, application, network, audit, page, connection, incident, infrastructure, or endpoint. Grant only the endpoints you enable.

Azure Monitor and Entra diagnostic logs exported to Event Hubs use the Event Hubs row. Reading those exported logs does not require a Graph AuditLog.Read.All grant.

nano permissions

Cloud pull sources need source_configs:view to list, source_configs:create to add, source_configs:edit to change, source_configs:deploy to deploy and source_configs:delete to remove. Attaching a credential also needs credentials:use; entering one needs credentials:create.

Pull feeds (SaaS collectors) need credentials:use to bind a credential, and credentials:create to enter a new one with the feed. Starting a feed (create or resume) needs log_sources:deploy and an enabled, deployed parser for every log source the feed emits into.

What's next

On this page