SecureAssure Platform Security Documentation | Last Updated: March 2026
All communications use TLS 1.2+ via HTTPS. WebSocket connections (Socket.IO) are encrypted over WSS. No plaintext HTTP connections accepted in production.
PostgreSQL database encrypted at storage layer. Client-side data stored in localStorage with application-level ECDSA P-256 signatures via Web Crypto API for integrity verification.
Per-user ECDSA P-256 keypairs generated locally using Web Crypto API. Private keys never leave the device. Public key hashes registered server-side for identity verification.
| Vector | Threat | Mitigation | Status |
|---|---|---|---|
| API Endpoints | Injection, abuse, DDoS | Input validation (Zod schemas), IP-based rate limiting (10 req/hr for reports, 30/hr for reputation), request size limits | LIVE |
| Community Reports | False reports, spam, coordinated manipulation | Trust scoring, community voting, auto-flagging (3+ downvotes at 3:1 ratio), IP tracking, rate limiting | LIVE |
| Client-Side Data | localStorage tampering, XSS | CSP headers, crypto-signed data integrity checks, no inline script execution, input sanitization | LIVE |
| WebSocket | Message spoofing, session hijack | WSS encryption, session-bound Socket.IO with reconnection tokens, server-side message validation | LIVE |
| File Uploads | Malware, oversized files | Type validation (60+ allowed types), size limits, filename sanitization, server-side MIME checking | LIVE |
| Authentication | Credential stuffing, brute force | Bcrypt password hashing, rate-limited login attempts, Stripe-integrated session management | LIVE |
The platform implements multi-tier access control:
| Role | Access Level | Capabilities |
|---|---|---|
| Public User | Free Tier | Core safety features, community reporting, basic monitoring |
| Pro User | Subscription | Tracker detection, deep scan, advanced analytics, travel safety |
| Enterprise Operator | Organization | ATLAS platform access, multi-user coordination, mission profiles, federal data feeds |
| Mission Commander | Profile-Based | Role-filtered dashboards (Emergency Manager, SAR Lead, Cyber Analyst, Field Engineer) |
| Defense Operator | Access-Gated | Defense modules require explicit access code authentication; separated from civilian capabilities |
All security-relevant actions are recorded in an append-only audit log stored in PostgreSQL:
Audit logs include: timestamp, actor identifier, action type, resource affected, request details, and source IP address. Logs are queryable via API with pagination and filtering support.
| Data Type | Retention | Purge Method |
|---|---|---|
| Community safety reports | 365 days | Auto-archive after expiry, manual purge on request |
| Panic events | 365 days | Immutable for investigation period, then archived |
| Audit logs | 730 days (2 years) | Append-only, no modification permitted |
| Session/analytics data | 90 days | Rolling window, aggregated then purged |
| Client-side localStorage | User-controlled | Data Ownership Dashboard provides one-click purge |
| Reputation database | 180 days per entry | Crowd-sourced data refreshed continuously |
| Uploaded files/media | 30 days or session | Auto-cleanup on session end or TTL expiry |
TLS encryption, input validation, rate limiting, RBAC, audit logging, vulnerability scanning pipeline.
Offline-first PWA architecture, service worker caching, multi-CDN static hosting, health monitoring endpoints.
Data classification framework, encryption key rotation, DLP controls, access review procedures.
Input validation pipeline, data quality checks, error handling with client error reporting, reconciliation procedures.
Privacy impact assessment, consent management, data minimization, user-controlled data export and purge.
| Metric | Target | Strategy |
|---|---|---|
| RTO (Recovery Time Objective) | < 4 hours | Automated redeployment from version control, database point-in-time recovery |
| RPO (Recovery Point Objective) | < 1 hour | Continuous PostgreSQL WAL archiving, real-time backup |
| Offline Resilience | Indefinite | PWA service worker caches core functionality, local data survives server outage |
The offline-first architecture ensures critical safety features (panic button, SafeWalk, tracker detection, cached maps) remain operational during server downtime. Data queued offline syncs automatically on reconnection.
| Metric | Target | Measured |
|---|---|---|
| Initial Page Load (PWA) | < 3s on 3G | ~2.1s (cached), ~3.4s (first load) |
| WebSocket Connection | < 500ms | ~120ms (domestic), ~400ms (international) |
| Federal Data Feed Latency | < 5s per source | ~1-3s (NASA, USGS, NOAA), ~2-5s (FEMA, CISA) |
| Offline Cache Size | < 50MB | ~12MB core + map tiles variable |
| Concurrent Users (Socket.IO) | 100+ per room | Tested to 50 concurrent; horizontal scaling via Redis adapter planned |
| Audit Log Write | < 50ms | ~8ms average (async, non-blocking) |
Browser-based deployment via Replit/cloud hosting. No installation required. Suitable for evaluation, training, and civilian operations.
Self-hosted Node.js + PostgreSQL on organizational infrastructure. Full data sovereignty. Air-gapped network compatible.
Docker/Kubernetes deployment for elastic scaling. Helm charts for automated provisioning. STIG-hardened base images.
SecureAssure - Veteran-Owned | security@secureassure.com