Skip to main content
IAM Policy Map

AWSSecurityIncidentResponseFullAccess

AdminAWS managedActivePermissions reviewedShow on mapCompare

Summary

Policy provides customers with Read and Write permissions to all resources associated to the Security Incident Response service.

Permissions imported from the AWS Managed Policy Reference Guide; other sections pending editorial review.

Identity

ARN
arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess
Default version
v4
Created
Last edited
Services
iam, organizations, security-ir

Control-plane actions (36)

By access level: 9 List, 12 Read, 2 Tagging, 13 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
IAM1 of 1901 Write; 1 restricted, 1 conditionaliam:CreateServiceLinkedRole
Organizations10 of 637 List, 3 Read; 0 restricted, 0 conditionalorganizations:DescribeAccount, organizations:DescribeOrganization, organizations:DescribeOrganizationalUnit, organizations:ListAWSServiceAccessForOrganization, organizations:ListAccounts, organizations:ListAccountsForParent, organizations:ListChildren, organizations:ListDelegatedAdministrators, organizations:ListOrganizationalUnitsForParent, organizations:ListRoots
Security Incident ResponseAll 25 actions (see the Security Incident Response page)2 List, 9 Read, 2 Tagging, 12 Write; 0 restricted, 0 conditionalsecurity-ir:*
IAM: 1 actions
  • iam:CreateServiceLinkedRole (Write)
Organizations: 10 actions
  • organizations:DescribeAccount (Read)
  • organizations:DescribeOrganization (Read)
  • organizations:DescribeOrganizationalUnit (Read)
  • organizations:ListAWSServiceAccessForOrganization (List)
  • organizations:ListAccounts (List)
  • organizations:ListAccountsForParent (List)
  • organizations:ListChildren (List)
  • organizations:ListDelegatedAdministrators (List)
  • organizations:ListOrganizationalUnitsForParent (List)
  • organizations:ListRoots (List)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: mixed.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants at least 80% of the write and permissions-management actions of: security-ir (12 of 12).

Guidance

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Same service

Same domain

Frequently asked questions

Pending editorial review. The permission data on this page comes straight from AWS; this section will be filled in once a reviewed guide exists.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "SecurityIRFullAccess",
      "Effect": "Allow",
      "Action": [
        "security-ir:*"
      ],
      "Resource": "*"
    },
    {
      "Sid": "AllowCreationOfServiceLinkedRoleForSecurityIncidentResponse",
      "Effect": "Allow",
      "Action": [
        "iam:CreateServiceLinkedRole"
      ],
      "Resource": [
        "arn:aws:iam::*:role/aws-service-role/security-ir.amazonaws.com/AWSServiceRoleForSecurityIncidentResponse"
      ],
      "Condition": {
        "StringLike": {
          "iam:AWSServiceName": "security-ir.amazonaws.com"
        }
      }
    },
    {
      "Sid": "AllowCreationOfServiceLinkedRoleForSecurityIncidentResponseTriage",
      "Effect": "Allow",
      "Action": [
        "iam:CreateServiceLinkedRole"
      ],
      "Resource": [
        "arn:aws:iam::*:role/aws-service-role/triage.security-ir.amazonaws.com/AWSServiceRoleForSecurityIncidentResponse_Triage"
      ],
      "Condition": {
        "StringLike": {
          "iam:AWSServiceName": "triage.security-ir.amazonaws.com"
        }
      }
    },
    {
      "Sid": "OrganizationsPolicies",
      "Effect": "Allow",
      "Action": [
        "organizations:DescribeOrganization",
        "organizations:ListDelegatedAdministrators",
        "organizations:ListAWSServiceAccessForOrganization",
        "organizations:ListRoots",
        "organizations:ListOrganizationalUnitsForParent",
        "organizations:ListAccountsForParent",
        "organizations:ListChildren",
        "organizations:DescribeOrganizationalUnit",
        "organizations:ListAccounts",
        "organizations:DescribeAccount"
      ],
      "Resource": "*"
    }
  ]
}

Version history

Current version v4, edited by AWS on 2026-04-22. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "awssecurityincidentresponsefullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AWSSecurityIncidentResponseFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AWSSecurityIncidentResponseFullAccess"),
);

Sources

Pending editorial review. No editorial sources are listed yet.