OpenISP
← Back to OpenISP

Security Policy & Data Protection - OpenISP

Last Updated: September 13, 2026
Version: 1.0


1. INTRODUCTION

The OpenISP Security Policy outlines how OpenISP protects your data, systems, and infrastructure from unauthorized access, misuse, and threats. This policy applies to:


2. SECURITY ARCHITECTURE

2.1 Defense-in-Depth Model

OpenISP implements multiple layers of security:

┌─────────────────────────────────────────────────────┐
│ Layer 1: Perimeter Security (Firewall, WAF, DDoS)   │
├─────────────────────────────────────────────────────┤
│ Layer 2: Network Security (TLS, VPN, Segmentation)  │
├─────────────────────────────────────────────────────┤
│ Layer 3: Application Security (Auth, Input Validation) │
├─────────────────────────────────────────────────────┤
│ Layer 4: Data Security (Encryption, Backup, Redaction) │
├─────────────────────────────────────────────────────┤
│ Layer 5: Physical Security (Data Center, Access)    │
├─────────────────────────────────────────────────────┤
│ Layer 6: Operational Security (Monitoring, Incident Response) │
└─────────────────────────────────────────────────────┘

3. ENCRYPTION & CRYPTOGRAPHY

3.1 Encryption Standards

Data State Algorithm Standard Key Size
Transit (TLS) AES-256-GCM TLS 1.3+ 256-bit
Transit (VPN) ChaCha20-Poly1305 WireGuard 256-bit
Stored (Passwords) Argon2id OWASP Variable salt
Stored (Sensitive Data) AES-256-CBC FIPS 140-2 256-bit
Database Backup AES-256 Encryption at rest 256-bit
File Upload AES-256-GCM OpenSSL 256-bit

3.2 Encrypted Data Fields

The following fields are encrypted at rest:

Tenant Data:

Subscriber Data:

3.3 Encryption Key Management

Key Type Generation Storage Rotation Access
Master Key Random 256-bit Hardware Security Module (HSM) Annual Root only
Database Key Derived from Master HSM-backed key vault Annual DB service only
TLS Private Key RSA 2048-bit Encrypted on disk Annual TLS service only
Session Keys Generated per session Memory only Per session Current request only

Key Backup: Master keys backed up to secure, geographically distributed vaults. Encryption keys never transmitted in plaintext.

3.4 Cipher Suites

TLS 1.3 Preferred Cipher Suite (in order):

  1. TLS_AES_256_GCM_SHA384
  2. TLS_AES_128_GCM_SHA256
  3. TLS_CHACHA20_POLY1305_SHA256

Legacy Support (TLS 1.2):

  1. ECDHE-ECDSA-AES256-GCM-SHA384
  2. ECDHE-ECDSA-AES128-GCM-SHA256

Explicitly Disabled: NULL, EXPORT, anon-DH, DES, RC4, MD5


4. AUTHENTICATION & ACCESS CONTROL

4.1 Authentication Methods

User Type Primary Method Secondary (2FA) Recovery
Tenant Admin Username/Password (Argon2id) TOTP or SMS Backup codes
Tenant Staff Username/Password TOTP or SMS Backup codes
Subscriber (PPPoE) Username/Password (encrypted) Optional TOTP Account email/phone
Subscriber (Hotspot) Mobile number (SMS/USSD) Optional Registration email
System Services API token (HMAC-SHA256) Mutual TLS (optional) Token rotation

4.2 Password Requirements

Tenant Admins:

Subscribers:

4.3 Multi-Factor Authentication (MFA)

MFA Methods:

MFA Enforcement:

Recovery:

4.4 Session Management

Aspect Requirement
Session Timeout 24 hours inactivity (re-login required)
Session ID 256-bit random, cryptographically secure
Cookie Flags HttpOnly, Secure, SameSite=Strict
Concurrent Sessions Max 5 per admin account (older sessions terminated)
Session Fixation Prevented (session ID regenerated after login)
CSRF Protection Token per-request, verified on state-changing operations

4.5 Role-Based Access Control (RBAC)

Platform Roles:

Role Permissions Scope
SuperAdmin All functions, cross-tenant view, policy changes Platform-wide
Tenant Owner Full account access, user management, billing, API keys Single tenant
Tenant Admin Dashboard, customer management, router configs, support Single tenant
Tenant Staff Limited dashboard, view-only analytics, basic support Single tenant
Customer Self-service portal, billing history, usage stats Single subscriber

Least Privilege: Each role has minimum permissions needed for function. Permissions cannot be combined/elevated except through role change.

4.6 API Authentication

API Token Format: openisp_[32 random characters]_[32 hash]

Aspect Requirement
Token Generation One per API key request, stored hashed (SHA-256)
Token Lifetime No expiration (manual revocation only) or custom expiration
Token Rotation Manual rotation recommended every 90 days
Token Scope Limited to specific operations (read, write, delete)
Rate Limiting 100-1000 requests/minute per token (depending on endpoint)
IP Whitelisting Optional per API key (recommended for production)
Mutual TLS Optional for high-security integrations

All application HTTP requests are also limited to 100 requests per minute per client IP. This broad ceiling covers public and authenticated traffic, including requests to unknown paths; stricter route-specific and user-specific limits still apply. Rate-limited requests receive HTTP 429 with a Retry-After value. This application-level protection complements, but does not replace, perimeter DDoS and WAF controls.


5. NETWORK SECURITY

5.1 HTTPS/TLS Enforcement

Requirements:

SSL Labs Rating Target: A+ (100/100 score)

5.2 Network Segmentation

┌────────────────────────────────────────────┐
│ DMZ (Public-facing)                         │
│ ├── Web app (reverse proxy)                │
│ ├── API Gateway (rate limiting)            │
│ └── DNS (resolvers)                        │
├────────────────────────────────────────────┤
│ Application Tier                            │
│ ├── Web servers (no internet access)       │
│ ├── API servers (no database direct access)│
│ └── Message queue (internal only)          │
├────────────────────────────────────────────┤
│ Database Tier                               │
│ ├── PostgreSQL (encrypted connections)    │
│ ├── Redis cache (memory only, no disk)    │
│ └── Key vault (hardware security module)  │
├────────────────────────────────────────────┤
│ Operational Tier                            │
│ ├── Logging service (centralized)         │
│ ├── Monitoring (observability)            │
│ └── Backup systems (air-gapped)           │
└────────────────────────────────────────────┘

Access Rules:

5.3 Firewall Rules

Inbound (Public):

Inbound (Admin VPN only):

Outbound (App → External):

Outbound (DB → External): Blocked (except backup to S3-like storage)

5.4 Reverse Proxy & WAF

Cloudflare/WAF Features:

Custom Rules:

5.5 DDoS Protection

Strategy:

Monitoring:


6. APPLICATION SECURITY

6.1 Secure Development Practices

Code Review:

Testing:

Dependencies:

6.2 Input Validation & Sanitization

Rule: All user input is untrusted until validated.

Validation:

Sanitization:

Example Invalid Inputs Rejected:

name: "<script>alert('xss')</script>"  // XSS attempt
email: "[email protected]' OR '1'='1"   // SQL injection attempt
phone: "+1 (555) 123-4567 DROP TABLE users;" // Injection
amount: "-999999"                       // Negative amount
date: "2099-13-45"                      // Invalid date

6.3 Output Encoding

HTML Context:

<!-- Input: <script>alert('xss')</script> -->
<!-- Output: &lt;script&gt;alert('xss')&lt;/script&gt; -->
<div>{{ user_input }}</div>

JavaScript Context:

// Input: '); alert('xss'); //
// Output: \'); alert(\'xss\'); //
var user = JSON.stringify(userInput);

URL Context:

// Input: /user/123?redirect=https://evil.com
// Output: /user/123?redirect=https%3A%2F%2Fevil.com

6.4 Cross-Site Request Forgery (CSRF) Protection

Implementation:

Example Flow:

1. User logs in → Session created, CSRF token generated
2. User visits form → CSRF token embedded in <form hidden>
3. User submits form → Token included in POST request
4. Server validates token before processing

6.5 Authentication Bypass Prevention

Protections:

6.6 Session Fixation Prevention

Protection:


7. DATA PROTECTION

7.1 Data Classification

Classification Examples Protection Level
Public Service documentation, public API docs Standard HTTPS
Internal System logs, internal metrics, IP addresses Encryption + access control
Confidential Passwords, API keys, RADIUS secrets Encryption + MFA + audit logging
Restricted Subscriber PII, payment data, health data Encryption + MFA + encryption at rest + minimal access

7.2 Data Minimization

Principle: Collect and retain only necessary data.

Application:

Deletion:

7.3 Data Retention Policy

Data Type Retention Period Reason
Active subscriber data Until deletion Current service
Deleted subscriber data 90 days Soft-delete recovery
Payment records 7 years Tax/audit compliance
RADIUS accounting 12 months Billing reconciliation
Access logs 6 months Security audit
Error logs 90 days Troubleshooting
Backups 30 days Disaster recovery
Support tickets 24 months Dispute resolution
Audit logs (admin actions) 12 months Change tracking

Purge Process:

7.4 Backup & Recovery

Backup Schedule:

Recovery SLA:

Backup Storage:

7.5 Data Portability

Tenants may request data export in standard formats:

Formats:

Process:

  1. Request via support portal [email protected]
  2. Verification of requestor identity (admin account required)
  3. Export generated and encrypted
  4. Download link provided (valid 7 days)
  5. Completion within 5 business days

Cost: Free for exports ≤ 1 GB; $100 per 10 GB for larger exports


8. INCIDENT RESPONSE

8.1 Incident Response Plan

Incident Response Team:

On-Call Schedule: 24/7/365 rotation, response within 15 minutes

8.2 Incident Categories & Response Times

Severity Definition Response SLA Example
Critical Active data breach, service down, ransomware 15 min Unauthorized database access in progress
High Data exposure (past breach), significant availability 1 hour Customer data exposed in logs
Medium Partial service issue, potential vulnerability 4 hours Weak TLS cipher suite enabled
Low No customer impact, informational 1 business day Configuration drift, minor log anomaly

8.3 Incident Response Steps

1. Detection & Triage (0-15 min)

2. Containment (15-60 min)

3. Investigation (1-24 hours)

4. Remediation (1-7 days)

5. Notification (24-72 hours)

6. Recovery (1-30 days)

7. Post-Incident (30+ days)

8.4 Breach Notification Timeline

Within 24 hours of discovery:

Within 72 hours:

Within 30 days:

Regulatory Notification:

8.5 Evidence Preservation

Chain of Custody:

Forensic Tools:


9. MONITORING & LOGGING

9.1 Centralized Logging

Logs Collected:

Log Aggregation:

Log Sanitization:

9.2 Security Monitoring

Alerts Triggered:

Response to Alerts:

9.3 Real-Time Monitoring

Metrics Tracked:

Dashboards:


10. VULNERABILITY MANAGEMENT

10.1 Vulnerability Identification

Sources:

10.2 Vulnerability Scoring

CVSS Scoring:

Internal Scoring Factors:

10.3 Patching Policy

Timing:

Process:

  1. Develop patch in isolated branch
  2. Test in staging environment (replicate production)
  3. Code review by security + development team
  4. Deployment to production (rolling update, no downtime)
  5. Monitor for issues (rollback plan on standby)
  6. Document patch + validate fix

Communication:


11. PHYSICAL SECURITY

11.1 Data Center Security

Facility Controls:

Environmental Controls:

Physical Safeguards:


12. COMPLIANCE & STANDARDS

12.1 Compliance Frameworks

OpenISP aligns with:

Framework Scope Status
ISO 27001 Information Security Management Aiming for certification
SOC 2 Type II Service Organization Controls Annual audit
GDPR EU data protection Compliant
CCPA California privacy Compliant
PCI-DSS Payment card security Compliant (scope: payment data handling)
HIPAA (if applicable) Health information protection Compliant (if processing health data)
NIST Cybersecurity Framework Risk management Aligned

12.2 Audit & Certification

Annual Audits:

Audit Reports:


13. SECURITY RESPONSIBILITIES

13.1 OpenISP Responsibilities

OpenISP provides:

OpenISP does NOT:

13.2 Tenant ISP Responsibilities

Tenants must:

13.3 Subscriber Responsibilities

Subscribers should:


14. SECURITY INCIDENT RESPONSE CONTACTS

14.1 Report a Security Issue

Security Email: [email protected]
PGP Key: Available at openisp.io/security/pgp (optional)
Response Time: Within 4 hours (critical issues)

14.2 Report a Vulnerability

Vulnerability Disclosure Policy: openisp.io/security/disclosure

Responsible Disclosure:

Recognition:

14.3 Emergency Contact

For critical security incidents:


15. SECURITY TRAINING & AWARENESS

15.1 Employee Security Training

All OpenISP staff receives:

Topics:

15.2 Tenant Security Guidance

OpenISP provides documentation:

Resource: support.openisp.io/security


16. SECURITY POLICY UPDATES

16.1 Policy Review & Updates

This policy is reviewed:

Notification: Material changes communicated to Tenants via email.


END OF SECURITY POLICY & DATA PROTECTION

Effective Date: [INSERT DATE]
Last Updated: September 13, 2026
Version: 1.0


APPENDIX: Security Checklist for Tenants

Pre-Production Checklist

Ongoing Maintenance