LOG-01: Enclave log exposure¶
| Property | Value |
|---|---|
| Severity | medium |
| Platform | AWS Nitro Enclaves |
| Lifecycle stage | runtime |
| Mode | Active: runs fixed read-only commands on the host. Skipped with --read-only. |
What it checks¶
It passes when:
- Journal logs are restricted to root.
Example failures:
- Enclave logs are accessible to non-root users: …
- Enclave logs are accessible to non-root users: Journal directory is world-readable (755)
How to fix¶
- Restrict journal access: chmod 750 /var/log/journal && remove non-essential users from the systemd-journal group. Consider forwarding enclave logs to a dedicated, access-controlled log pipeline.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No instance ID specified; skipping check.
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--instance-id |
EC2 instance ID running the Nitro Enclave. |
--region |
AWS region. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| AWS | ssm.get_command_invocation |
ssm:GetCommandInvocation |
read |
| AWS | ssm.send_command |
ssm:SendCommand |
run command |
Every AWS scan also calls sts:GetCallerIdentity. See Required permissions for a complete policy.
Evidence recorded¶
Keys in the finding's evidence: journal_group, journal_perms, journal_users
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).