docs: Rebuild documentation as enterprise-grade TLAS platform

- Migrate from custom HTTP server to VitePress framework
- Rename project to Tokenized License Approval System (TLAS)
- Add comprehensive documentation for all stakeholders:
  - Business: Executive summary, value proposition, governance
  - Operations: Infrastructure, installation, monitoring, backup
  - Departments: User guide, workflows, verification, issuance
  - Developers: API reference, authentication, webhooks, SDKs
  - Compliance: OWASP, DPDP Act, IT Act, audit framework
- Add modern theme with dark mode and full-text search
- Update Dockerfile for VitePress build process

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Mahi
2026-02-10 00:05:20 -04:00
parent 4a5bf16827
commit 435889ee79
65 changed files with 6324 additions and 8342 deletions

View File

@@ -0,0 +1,72 @@
# Compliance Framework
## Overview
TLAS is designed and operated in compliance with applicable Indian laws, government standards, and international security frameworks.
## Regulatory Compliance
### Information Technology Act, 2000
| Requirement | Implementation |
|-------------|----------------|
| Section 3A: Electronic signatures | Digital certificates with PKI |
| Section 4: Legal recognition of electronic records | Blockchain-based immutable records |
| Section 43A: Data protection | Encryption at rest and in transit |
| Section 72A: Breach notification | Incident response procedures |
### Digital Personal Data Protection Act, 2023
| Principle | Implementation |
|-----------|----------------|
| Lawful purpose | Data collected only for licensing functions |
| Purpose limitation | No secondary use without consent |
| Data minimization | Only necessary fields collected |
| Accuracy | Applicant can update their information |
| Storage limitation | Defined retention periods |
| Security safeguards | Technical and organizational measures |
### Government Guidelines
| Standard | Compliance |
|----------|------------|
| GIGW 3.0 | Web accessibility guidelines followed |
| MeitY Cloud Guidelines | Data residency in India |
| NIC Security Guidelines | Network and application security |
## Security Standards
### OWASP Top 10 Mitigation
| Vulnerability | Control |
|---------------|---------|
| Injection | Parameterized queries, input validation |
| Broken Authentication | JWT with secure configuration |
| Sensitive Data Exposure | TLS 1.3, AES-256 encryption |
| XML External Entities | XML parsing disabled where not needed |
| Broken Access Control | RBAC with principle of least privilege |
| Security Misconfiguration | Hardened deployment checklist |
| Cross-Site Scripting | Output encoding, CSP headers |
| Insecure Deserialization | Schema validation |
| Components with Vulnerabilities | Automated dependency scanning |
| Insufficient Logging | Comprehensive audit logging |
### ISO 27001 Alignment
TLAS security controls align with ISO 27001 Annex A:
- A.5: Information security policies
- A.6: Organization of information security
- A.9: Access control
- A.10: Cryptography
- A.12: Operations security
- A.14: System acquisition and development
- A.16: Incident management
- A.18: Compliance
## Documentation Index
- [Data Protection](/compliance/data-protection) - Personal data handling procedures
- [Audit Framework](/compliance/audit) - Logging, monitoring, and audit procedures
- [Security Standards](/compliance/security) - Technical security controls
- [Regulatory Alignment](/compliance/regulatory) - Detailed compliance mapping