Agent Skills
› serithemage/serverless-openclaw
› security
security
GitHub提供Serverless应用安全模型参考，涵盖Bridge防御、IDOR防护、密钥管理、Cognito认证及IAM最小权限。作为编写或审查代码时的安全检查清单，确保系统安全性。
Trigger Scenarios
编写涉及身份验证的代码
审查代码中的权限配置
检查敏感信息存储方式
设计API网关安全策略
Install
npx skills add serithemage/serverless-openclaw --skill security -g -y
SKILL.md
Frontmatter
{
"name": "security",
"description": "References Serverless OpenClaw security model. Covers Bridge 6-layer defense, IDOR prevention, secret management, Cognito authentication, and IAM least privilege. Use as a security checklist when writing or reviewing code.",
"allowed-tools": "Read, Glob, Grep"
}
Security Reference
Security Model Details
Authentication, Bridge defense, IDOR prevention, secret management, IAM roles:
- architecture.md §7 — Bridge defense, authentication, IDOR, secrets, IAM
Security Checklist (For Code Writing/Review)
Bridge Server
- Bearer token authentication applied to all endpoints except
/health - TLS (self-signed) applied (
https.createServer) - Gateway bound to
--bind localhostto block external access - Running as non-root user (
USER openclaw) -
/healthreturns only{ "status": "ok" }(no internal info exposure)
Secrets
- API keys/tokens NOT written to
openclaw.json - Using
config.auth = { method: "env" } -
delete config.auth?.apiKeyapplied -
delete config.gateway?.auth?.tokenapplied - Delivered only via Secrets Manager → environment variables
IDOR
- userId determined server-side (JWT
subor connectionId reverse lookup) - Client-provided userId not trusted
- DynamoDB query PK uses
jwt.sub
Authentication
- WebSocket:
?token={jwt}→ verified in ws-connect - REST API: Cognito User Pool Authorizer applied
- Telegram:
X-Telegram-Bot-Api-Secret-Tokenverification + pairing check
IAM
- Lambda: access only to required DynamoDB tables (resource ARN restricted)
- Fargate: access only to S3 data bucket
- ECS permissions: Condition restricted to specific cluster
- PassRole: only task-role and exec-role allowed
Lambda Agent (Phase 2)
See architecture.md §security for full Lambda security details.
- Lambda IAM least privilege:
S3:GetObject/PutObjectonsessions/*prefix only - Lambda IAM:
SSM:GetParameteronsecrets/*prefix only (no wildcard) - Lambda IAM:
DynamoDB:GetItem/PutItem/DeleteItemon TaskState table only - Lambda IAM:
cloudwatch:PutMetricDatafor custom metrics (namespace-restricted) -
SessionLockprevents concurrent Lambda invocations accessing same session - No secrets on disk:
HOME=/tmp, env vars only (never write API keys to files) - Lambda container: non-root user, read-only root filesystem where possible
Version History
- 504300d Current 2026-07-25 09:02
