Back to catalog
Static reviewDevelopment

Skill dossier

securing-serverless-functions

Source declaration

Hardens serverless compute platforms (AWS Lambda, Azure Functions, Google Cloud Functions): least-privilege IAM roles, dependency vulnerability scanning, secrets management integration, input validation, function URL authentication, and runtime monitoring. Use when deploying serverless functions with sensitive access, auditing for overly permissive roles, or adding functions to a DevSecOps pipeline.

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

Hardens serverless compute platforms (AWS Lambda, Azure Functions, Google Cloud Functions): least-privilege IAM roles, dependency vulnerability scanning, secrets management integration, input validation, function URL authentication, and runtime monitoring. Use when deploying serverless functions with sensitive access, auditing for overly permissive roles, or adding functions to a DevSecOps pipeline.

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 serverless compute platforms (AWS Lambda, Azure Functions, Google Cloud Functions): least-privilege IAM roles, dependency vulnerability scanning, secrets management integration, input validation, function URL authentication, and runtime monitoring. Use when deploying serverless functions with sensitive access, auditing for overly permissive roles, or adding functions to a DevSecOps pipeline. 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-serverless-functions/SKILL.md:L53]
  • Step 1: Enforce Least Privilege IAM Roles [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L55]
  • Step 2: Eliminate Hardcoded Secrets [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L98]
  • Step 3: Scan Dependencies for Vulnerabilities [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L137]
  • Step 4: Implement Input Validation [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L181]
  • Step 5: Configure Function URL and API Gateway Authentication [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L219]
  • Step 6: Enable Runtime Monitoring and Logging [Source statement; provisional, not tested. Evidence: skills/securing-serverless-functions/SKILL.md:L243]

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-serverless-functions/SKILL.md:L1-L32]

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
32.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/securing-serverless-functions/LICENSEOther11 KB
skills/securing-serverless-functions/references/api-reference.mdReference2.1 KB
skills/securing-serverless-functions/scripts/agent.pyScript7.1 KB
skills/securing-serverless-functions/SKILL.mdInstruction12.1 KB

SKILL.md frontmatter

{
  "name": "securing-serverless-functions",
  "description": "Hardens serverless compute platforms (AWS Lambda, Azure Functions, Google Cloud Functions): least-privilege IAM roles, dependency vulnerability scanning, secrets management integration, input validation, function URL authentication, and runtime monitoring. Use when deploying serverless functions with sensitive access, auditing for overly permissive roles, or adding functions to a DevSecOps pipeline.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "serverless-security",
    "aws-lambda",
    "azure-functions",
    "function-hardening",
    "supply-chain"
  ],
  "version": "1.0.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",
    "T1003"
  ]
}

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: Enforce Least Privilege IAM Roles

    Source-described action candidate under “Step 1: Enforce Least Privilege IAM Roles”; not verified execution.

  4. 04
    Action

    Step 2: Eliminate Hardcoded Secrets

    Source-described action candidate under “Step 2: Eliminate Hardcoded Secrets”; not verified execution.

  5. 05
    Action

    Step 3: Scan Dependencies for Vulnerabilities

    Source-described action candidate under “Step 3: Scan Dependencies for Vulnerabilities”; not verified execution.

  6. 06
    Input

    Step 4: Implement Input Validation

    Source-described input candidate under “Step 4: Implement Input Validation”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Input

    Validate and sanitize all event input data to prevent injection attacks including SQL injection, command injection, and NoSQL injection through Lambda event sources.

    Source-described input candidate under “Step 4: Implement Input Validation”; not verified execution.

  2. 08
    Action

    Step 5: Configure Function URL and API Gateway Authentication

    Source-described action candidate under “Step 5: Configure Function URL and API Gateway Authentication”; not verified execution.

  3. 09
    Action

    Step 6: Enable Runtime Monitoring and Logging

    Source-described action candidate under “Step 6: Enable Runtime Monitoring and Logging”; not verified execution.

  4. 10
    Action

    Key Concepts

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

  5. 11
    Action

    Tools & Systems

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

  6. 12
    Action

    Common Scenarios

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

  7. 13
    Action

    Audit the Lambda function code for string concatenation in SQL queries

    Source-described action candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  8. 14
    Action

    Replace all string-formatted queries with parameterized queries using the database driver

    Source-described action candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  9. 15
    Input

    Implement input validation using JSON Schema before any database operation

    Source-described input candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  10. 16
    Action

    Add a WAF rule on API Gateway to block common SQL injection patterns

    Source-described action candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  11. 17
    Action

    Deploy Semgrep in the CI/CD pipeline with the `python.django.security.injection.sql` rule set

    Source-described action candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  12. 18
    Action

    Enable GuardDuty Lambda protection to detect anomalous database connection patterns

    Source-described action candidate under “Scenario: SQL Injection via API Gateway to Lambda to RDS”; not verified execution.

  13. 19
    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.

Attention recommended

15 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 useObserved
Medium

Network access is mentioned

7 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 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.

Note

File modification is described or implemented

4 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 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

4 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 4 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-serverless-functions/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-serverless-functions/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-serverless-functions
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.