Back to catalog
Static reviewDevelopment

Skill dossier

implementing-aws-nitro-enclave-security

Source declaration

Build AWS Nitro Enclave confidential computing environments using nitro-cli to create enclave images, configure attestation-aware KMS policies with PCR condition keys, validate attestation documents against the Nitro PKI root, and set up vsock/kmstool-enclave-cli pipelines for processing PII, keys, and health records. Use for Nitro Enclave setup, attestation validation, or scoping KMS to an enclave image hash.

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

Build AWS Nitro Enclave confidential computing environments using nitro-cli to create enclave images, configure attestation-aware KMS policies with PCR condition keys, validate attestation documents against the Nitro PKI root, and set up vsock/kmstool-enclave-cli pipelines for processing PII, keys, and health records. Use for Nitro Enclave setup, attestation validation, or scoping KMS to an enclave image hash.

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.

Build AWS Nitro Enclave confidential computing environments using nitro-cli to create enclave images, configure attestation-aware KMS policies with PCR condition keys, validate attestation documents against the Nitro PKI root, and set up vsock/kmstool-enclave-cli pipelines for processing PII, keys, and health records. Use for Nitro Enclave setup, attestation validation, or scoping KMS to an enclave image hash. 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/implementing-aws-nitro-enclave-security/SKILL.md:L56]
  • Step 1: Configure the Nitro Enclaves Environment [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L58]
  • Step 2: Build the Enclave Image File (EIF) [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L80]
  • Step 3: Configure KMS Attestation-Based Key Policies [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L125]
  • Step 4: Implement Secure Vsock Communication [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L177]
  • Step 5: Validate Attestation Documents [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L280]
  • Step 6: Launch and Monitor the Enclave [Source statement; provisional, not tested. Evidence: skills/implementing-aws-nitro-enclave-security/SKILL.md:L337]

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/implementing-aws-nitro-enclave-security/SKILL.md:L1-L34]

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

File inventory

PathTypeBytes
skills/implementing-aws-nitro-enclave-security/LICENSEOther11 KB
skills/implementing-aws-nitro-enclave-security/references/api-reference.mdReference4 KB
skills/implementing-aws-nitro-enclave-security/scripts/agent.pyScript20.6 KB
skills/implementing-aws-nitro-enclave-security/SKILL.mdInstruction21.3 KB

SKILL.md frontmatter

{
  "name": "implementing-aws-nitro-enclave-security",
  "description": "Build AWS Nitro Enclave confidential computing environments using nitro-cli to create enclave images, configure attestation-aware KMS policies with PCR condition keys, validate attestation documents against the Nitro PKI root, and set up vsock/kmstool-enclave-cli pipelines for processing PII, keys, and health records. Use for Nitro Enclave setup, attestation validation, or scoping KMS to an enclave image hash.\n",
  "domain": "cybersecurity",
  "subdomain": "cloud-security",
  "tags": [
    "AWS-Nitro-Enclaves",
    "confidential-computing",
    "attestation",
    "KMS",
    "enclave-isolation",
    "vsock",
    "PCR"
  ],
  "version": "1.0.0",
  "author": "mukul975",
  "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",
    "T0816"
  ]
}

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: Configure the Nitro Enclaves Environment

    Source-described action candidate under “Step 1: Configure the Nitro Enclaves Environment”; not verified execution.

  4. 04
    Action

    Install the Nitro Enclaves CLI: On Amazon Linux 2, install the tools and allocator:

    Source-described action candidate under “Step 1: Configure the Nitro Enclaves Environment”; not verified execution.

  5. 05
    Action

    Configure memory and CPU allocation: Edit `/etc/nitroenclaves/allocator.yaml` to reserve resources for the enclave. The enclave requires dedicated memory that is carved from the parent instance:

    Source-described action candidate under “Step 1: Configure the Nitro Enclaves Environment”; not verified execution.

  6. 06
    Action

    Verify setup: Run `nitro-cli describe-enclaves` to confirm the CLI can communicate with the Nitro hypervisor. An empty JSON array `[]` indicates no enclaves are running and the setup is correct.

    Source-described action candidate under “Step 1: Configure the Nitro Enclaves Environment”; not verified execution.

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

    Step 2: Build the Enclave Image File (EIF)

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  2. 08
    Action

    Create the application Dockerfile: The enclave runs a minimal Linux environment. The application communicates exclusively through vsock:

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  3. 09
    Action

    Build the EIF with nitro-cli: Convert the Docker image into an enclave image file, capturing the PCR measurements:

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  4. 10
    Action

    PCR0: SHA-384 hash of the enclave image file (the full image digest)

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  5. 11
    Action

    PCR1: SHA-384 hash of the Linux kernel and bootstrap process

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  6. 12
    Action

    PCR2: SHA-384 hash of the application code

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  7. 13
    Action

    Build a signed EIF (recommended for production): Generate a signing certificate and use it to produce PCR8:

    Source-described action candidate under “Step 2: Build the Enclave Image File (EIF)”; not verified execution.

  8. 14
    Action

    Step 3: Configure KMS Attestation-Based Key Policies

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  9. 15
    Action

    Create a KMS key policy that restricts decryption to a verified enclave:

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  10. 16
    Action

    Policy using PCR0 (image hash): This locks the key to a specific enclave build. Any code change produces a new PCR0, requiring a policy update:

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  11. 17
    Action

    Policy using PCR8 (signing certificate): Trusts any enclave signed with a specific certificate, enabling image rotation without policy changes:

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  12. 18
    Action

    Multi-PCR policy for defense in depth: Combine PCR0 (image) and PCR1 (kernel) to ensure both the application and the boot environment match expected values:

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  13. 19
    Action

    IAM role policy: The parent instance's IAM role must have `kms:Decrypt` permission, but the KMS key policy condition ensures the actual decryption only succeeds when the request originates from a valid enclave with the correct attestation document attached.

    Source-described action candidate under “Step 3: Configure KMS Attestation-Based Key Policies”; not verified execution.

  14. 20
    Action

    Step 4: Implement Secure Vsock Communication

    Source-described action candidate under “Step 4: Implement Secure Vsock Communication”; not verified execution.

  15. 21
    Action

    Vsock architecture: The only way an enclave communicates with the outside world is through a vsock (virtual socket). Vsock uses a CID (Context Identifier) and port number. The parent instance CID is always `3`, and the enclave CID is assigned at launch.

    Source-described action candidate under “Step 4: Implement Secure Vsock Communication”; not verified execution.

  16. 22
    Action

    Parent-side proxy server: The parent runs a proxy that forwards KMS API calls from the enclave through the vsock to the AWS KMS endpoint:

    Source-described action candidate under “Step 4: Implement Secure Vsock Communication”; not verified execution.

  17. 23
    Action

    Enclave-side client: The enclave application requests an attestation document from the Nitro Security Module (NSM) device at `/dev/nsm`, attaches it to KMS decrypt requests, and receives data encrypted to the enclave's ephemeral public key:

    Source-described action candidate under “Step 4: Implement Secure Vsock Communication”; not verified execution.

  18. 24
    Action

    Step 5: Validate Attestation Documents

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  19. 25
    Action

    Attestation document structure: The document is CBOR-encoded and COSE-signed (COSESign1). It contains:

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  20. 26
    Action

    `moduleid`: Identifier for the NSM module

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  21. 27
    Action

    `digest`: Hashing algorithm (SHA-384)

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  22. 28
    Action

    `timestamp`: Unix epoch milliseconds when the document was created

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  23. 29
    Action

    `pcrs`: Map of PCR index to measurement value (PCR0-PCR15)

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  24. 30
    Action

    `certificate`: The NSM's x509 certificate, signed by the Nitro PKI

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  25. 31
    Action

    `cabundle`: Certificate chain from the NSM certificate to the AWS Nitro root CA

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  26. 32
    Input

    `publickey`: The enclave's ephemeral public key (provided at attestation request time)

    Source-described input candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  27. 33
    Action

    `userdata`: Optional application-defined data (up to 512 bytes)

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  28. 34
    Action

    `nonce`: Optional nonce for freshness verification

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  29. 35
    Action

    Validation steps:

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  30. 36
    Action

    Decode the COSESign1 structure and extract the payload and certificate

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  31. 37
    Action

    Verify the COSE signature using the public key from the embedded certificate

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  32. 38
    Action

    Validate the certificate chain from the NSM certificate through the CA bundle to the AWS Nitro Attestation PKI root certificate (available at `https://aws-nitro-enclaves.amazonaws.com/AWSNitroEnclavesRoot-G1.zip`)

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  33. 39
    Action

    Check that the root CA certificate matches the expected AWS root: `aws.nitro-enclaves` CN

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  34. 40
    Action

    Verify that no certificate in the chain is expired at the document's timestamp

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  35. 41
    Output

    Compare PCR0, PCR1, PCR2 values against expected measurements from the enclave build output

    Source-described output candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  36. 42
    Decision

    If a nonce was provided, verify it matches to prevent replay attacks

    Source-described decision candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  37. 43
    Action

    Attestation validation code:

    Source-described action candidate under “Step 5: Validate Attestation Documents”; not verified execution.

  38. 44
    Action

    Step 6: Launch and Monitor the Enclave

    Source-described action candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  39. 45
    Action

    Run the enclave and implement operational monitoring:

    Source-described action candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  40. 46
    Action

    Launch the enclave:

    Source-described action candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  41. 47
    Action

    Verify enclave status:

    Source-described action candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  42. 48
    Input

    Read enclave console (debug mode only):

    Source-described input candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  43. 49
    Action

    Terminate the enclave:

    Source-described action candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  44. 50
    Output

    CloudWatch monitoring: Configure the parent instance to report enclave health metrics. Since the enclave has no network access, health checks must go through the vsock proxy:

    Source-described output candidate under “Step 6: Launch and Monitor the Enclave”; not verified execution.

  45. 51
    Action

    Key Concepts

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

  46. 52
    Action

    Tools & Systems

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

  47. 53
    Action

    Common Scenarios

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

  48. 54
    Action

    Build the tokenization application into a Docker image containing the tokenization logic, the `kmstool-enclave-cli` binary, and a vsock server that accepts encrypted records

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  49. 55
    Output

    Build the EIF with `nitro-cli build-enclave` and record PCR0, PCR1, PCR2 from the build output

    Source-described output candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  50. 56
    Action

    Create a KMS key with a key policy that includes a `kms:RecipientAttestation:ImageSha384` condition matching PCR0, allowing only this specific enclave build to decrypt patient records

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  51. 57
    Action

    Deploy the parent instance with an IAM role that has `kms:Decrypt` on the key, but the KMS condition ensures decryption only succeeds inside the attested enclave

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  52. 58
    Action

    The parent application receives encrypted patient records over HTTPS, passes them to the enclave over vsock port 5000, and receives tokenized records back

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  53. 59
    Action

    The enclave requests an attestation document from the NSM, attaches it to the KMS Decrypt call, receives the plaintext encrypted to its ephemeral RSA key, decrypts locally, tokenizes PII (SSN, DOB, name), and returns `{ssn: "toka8f3...", dob: "tokb2e1...", name: "tokc9d4..."}`

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

  54. 60
    Action

    CloudTrail logs show `Decrypt` calls with `RecipientAttestation` parameters, confirming all decryption occurs within the enclave boundary

    Source-described action candidate under “Scenario: Implementing a PII Tokenization Service in a Nitro Enclave”; not verified execution.

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

26 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

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

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

Elevated privileges are referenced

7 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. 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/implementing-aws-nitro-enclave-security/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/implementing-aws-nitro-enclave-security/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/implementing-aws-nitro-enclave-security
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.