Security & Privacy
Relevant source files
The following files were used as context for generating this wiki page:
The security architecture of the bl1nk platform is centered around a multi-layered defense strategy designed to protect sensitive user data, API credentials, and cloud infrastructure. The system incorporates automated security scanning, proactive vulnerability identification through specialized AI roles, and rigorous data handling practices such as encryption and secret management.
Privacy and security efforts are integrated directly into the development lifecycle, ranging from initial design requirements to continuous integration (CI) pipelines that perform dependency, code, and secret analysis.
Sources: Comprehensive.md:8-15, specs/main/plan.md:10-15
Security Analysis Framework
The platform utilizes a specialized security expert role to identify vulnerabilities that could lead to data breaches or unauthorized access. This role focuses on four primary domains: Authentication & Authorization, Injection Attacks, API Security, and Client-Side Secrets.
Vulnerability Severity Matrix
The following table defines the impact levels used during security reviews:
| Level | Description |
|---|---|
| Critical | Actively exploitable or trivially exploitable, leading to full system or data compromise with no mitigation in place. |
| High | Exploitable with some conditions; could lead to significant data exposure, account takeover, or service disruption. |
| Medium | Vulnerability increases exposure or weakens defenses, but exploitation requires multiple steps or sophistication. |
| Low | Low immediate risk; typically requires local access or only violates best practices without a clear exploitation path. |
Sources: apps/client/src/prompts/security_review_prompt.ts:35-39, tests/e2e/fixtures/security-review/findings.md:1-122
Security Review Flow
This diagram illustrates the automated process of scanning and reporting findings within the platform.
The review process prioritizes client-side exposed secrets and data leaks over availability-only issues (e.g., site downtime).
Sources: apps/client/src/prompts/security_review_prompt.ts:5-46
Secret Management & Infrastructure
Infrastructure security is maintained through strict credential handling and automated scanning of the codebase for leaked secrets.
Encryption and Credentials
The platform manages various credentials, including ApiCredential sets which are stored in an encrypted state. A critical security rule is the absolute prohibition of hardcoded credentials (such as AWS access keys or JWT secrets) within the source code.
Sources: Comprehensive.md:58-61, tests/e2e/fixtures/security-review/findings.md:46-56
Automated Infrastructure Protection
Implementation Standards
During the design and task planning phases (via the Kiro or Spec-Kit workflows), security is treated as a core non-functional requirement.
Design Principles
Architectural decisions are governed by a project-specific "Constitution" and specific security considerations:
- Authentication: Implementation of secure middleware and JWT strategies using strong random secrets.
- Authorization: Role-Based Access Control (RBAC) to protect sensitive administrative endpoints.
- Data Protection: Whitelisting allowed file extensions and validating content types during uploads to prevent malicious execution.
- Error Handling: Suppressing verbose stack traces in production to prevent information leakage of the internal application structure.
Sources: plugins/kiro-skill/skills/kiro-skill/SKILL.md:145-150, tests/e2e/fixtures/security-review/findings.md:13-120
Required Security Configuration
| Secret Key | Purpose |
|---|---|
APPLE_PASSWORD | Used for macOS notarization and code signing. |
SM_CODE_SIGNING_CERT_SHA1_HASH | Digital signature hash for Windows builds. |
SNYK_TOKEN | Dependency vulnerability scanning. |
SONAR_TOKEN | Code quality and static security analysis. |
JWT_SECRET | Environment variable (not hardcoded) for session tokens. |
Sources: Comprehensive.md:141-160, specs/main/plan.md:255-275
Conclusion
The security and privacy framework is integrated through every stage of the platform, from the "Constitution" that guides development to the automated GitHub Actions workflows that monitor production code. By prioritizing the prevention of data breaches and credential theft, the project maintains a high standard of protection for both users and the underlying cloud infrastructure.