Back to catalog
Static reviewDevelopment

Skill dossier

securing-aws-lambda-execution-roles

Source declaration

Hardens AWS Lambda execution roles by writing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, validating permissions with IAM Access Analyzer, and enforcing role scoping through SCPs. Use when deploying new Lambda functions, remediating overly permissive Lambda roles found in an audit, or building reusable least-privilege IAM role templates for serverless teams.

The author's original description, preserved in English. It describes intent, not verified performance.

Hardens AWS Lambda execution roles by writing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, validating permissions with IAM Access Analyzer, and enforcing role scoping through SCPs. Use when deploying new Lambda functions, remediating overly permissive Lambda roles found in an audit, or building reusable least-privilege IAM role templates for serverless teams.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Hardens AWS Lambda execution roles by writing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, validating permissions with IAM Access Analyzer, and enforcing role scoping through SCPs. Use when deploying new Lambda functions, remediating overly permissive Lambda roles found in an audit, or building reusable least-privilege IAM role templates for serverless teams. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L55]
  • Step 1: Audit Current Lambda Execution Role Permissions [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L57]
  • Step 2: Analyze Actual API Usage with CloudTrail [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L85]
  • Step 3: Create Least-Privilege Execution Policies [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L115]
  • Step 4: Apply Permission Boundaries [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L192]
  • Step 5: Validate Policies with IAM Access Analyzer [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L244]
  • Step 6: Enforce Role Standards with SCPs [Source statement; provisional, not tested. Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L268]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L1-L33]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
33.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/securing-aws-lambda-execution-roles/LICENSEOther11 KB
skills/securing-aws-lambda-execution-roles/references/api-reference.mdReference2.3 KB
skills/securing-aws-lambda-execution-roles/scripts/agent.pyScript7.1 KB
skills/securing-aws-lambda-execution-roles/SKILL.mdInstruction13 KB

SKILL.md frontmatter

{
  "name": "securing-aws-lambda-execution-roles",
  "description": "Hardens AWS Lambda execution roles by writing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, validating permissions with IAM Access Analyzer, and enforcing role scoping through SCPs. Use when deploying new Lambda functions, remediating overly permissive Lambda roles found in an audit, or building reusable least-privilege IAM role templates for serverless teams.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "cloud-security",
    "aws",
    "lambda",
    "iam",
    "least-privilege",
    "execution-roles"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.IR-01",
    "ID.AM-08",
    "GV.SC-06",
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1078.004",
    "T1530",
    "T1537",
    "T1580"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Audit Current Lambda Execution Role Permissions

    Source-described action candidate under “Step 1: Audit Current Lambda Execution Role Permissions”; not verified execution.

  4. 04
    Action

    Step 2: Analyze Actual API Usage with CloudTrail

    Source-described action candidate under “Step 2: Analyze Actual API Usage with CloudTrail”; not verified execution.

  5. 05
    Action

    Use CloudTrail and IAM Access Analyzer to determine which API actions the function actually uses.

    Source-described action candidate under “Step 2: Analyze Actual API Usage with CloudTrail”; not verified execution.

  6. 06
    Action

    Step 3: Create Least-Privilege Execution Policies

    Source-described action candidate under “Step 3: Create Least-Privilege Execution Policies”; not verified execution.

Inspect all extracted workflow candidates (23 candidate steps)
  1. 07
    Action

    Step 4: Apply Permission Boundaries

    Source-described action candidate under “Step 4: Apply Permission Boundaries”; not verified execution.

  2. 08
    Action

    Step 5: Validate Policies with IAM Access Analyzer

    Source-described action candidate under “Step 5: Validate Policies with IAM Access Analyzer”; not verified execution.

  3. 09
    Action

    Use Access Analyzer to validate policies for security best practices.

    Source-described action candidate under “Step 5: Validate Policies with IAM Access Analyzer”; not verified execution.

  4. 10
    Action

    Step 6: Enforce Role Standards with SCPs

    Source-described action candidate under “Step 6: Enforce Role Standards with SCPs”; not verified execution.

  5. 11
    Action

    Apply Service Control Policies to prevent Lambda functions from using overly broad roles.

    Source-described action candidate under “Step 6: Enforce Role Standards with SCPs”; not verified execution.

  6. 12
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  7. 13
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  8. 14
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  9. 15
    Action

    Enable CloudTrail data events for Lambda to capture actual API usage per function

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  10. 16
    Action

    Wait 30 days to collect a representative sample of API calls

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  11. 17
    Action

    Use IAM Access Analyzer policy generation for each function's role usage

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  12. 18
    Action

    Create individual scoped policies for each function based on actual API usage

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  13. 19
    Action

    Apply permission boundaries to cap maximum permissions

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  14. 20
    Action

    Deploy scoped roles to staging and run integration tests

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  15. 21
    Action

    Roll out to production with canary deployment and rollback plan

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  16. 22
    Action

    Validate with IAM Policy Simulator before removing the old broad role

    Source-described action candidate under “Scenario: Reducing a Lambda Function from AdministratorAccess to Least Privilege”; not verified execution.

  17. 23
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

12 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

5 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

7 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/securing-aws-lambda-execution-roles/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/securing-aws-lambda-execution-roles/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/securing-aws-lambda-execution-roles
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.