1. Executive Security Philosophy
At Staff Scheduling, security is not an optional add-on—it is the foundational architectural pillar of our platform. Organizations trust us with business-critical workforce records: employee personally identifiable information (PII), shift rosters, geofenced attendance logs, hourly wage rates, and team communications.
We employ a Defense-in-Depth and Zero-Trust security architecture across every layer of our stack:
- Principle of Least Privilege: Every microservice, background job, and user role operates with the minimal set of permissions needed to execute its function.
- Zero Cross-Tenant Leakage: Multi-tenant isolation is enforced at the database query layer, ensuring strict organizational sandboxing.
- Defensive Engineering: Automated rate-limiting, brute-force mitigation, CSRF verification, and non-webroot media isolation protect our perimeter.
2. Cloud Infrastructure & Facility Security
Staff Scheduling runs on enterprise-grade cloud environments powered by LiteSpeed Enterprise web servers hosted within SOC 2 Type II and ISO 27001 certified data center facilities across North America.
🏢 Physical Perimeter Security
Biometric entry checkpoints, 24/7/365 armed guard patrols, man-traps, and continuous CCTV surveillance with 90-day archive retention.
⚡ Power & Environmental Redundancy
N+1 redundant UPS battery backups, on-site emergency diesel generators, automated HVAC climate controls, and inert gas fire suppression.
3. Data Encryption (TLS 1.3 & AES-256)
3.1 Encryption in Transit
All network communications between user devices and our servers are encrypted:
- TLS 1.3 Modern Ciphers: Modern TLS 1.3 is enforced with forward-secrecy cipher suites (e.g.,
ECDHE-RSA-AES128-GCM-SHA256). - HSTS Preloaded: HTTP Strict Transport Security (
max-age=31536000; includeSubDomains; preload) instructs browsers to permanently reject unencrypted HTTP connections. - Legacy Protocols Blocked: Insecure legacy protocols (SSL v2/v3, TLS 1.0, TLS 1.1) and weak ciphers (RC4, 3DES) are disabled at the edge proxy level.
3.2 Encryption at Rest
Customer relational databases, timesheet logs, and attendance media are encrypted at rest using AES-256 (Advanced Encryption Standard with 256-bit keys) applied at the block storage and filesystem layer.
3.3 Cryptographic Key Management
Encryption keys are managed independently of the application layer, rotated on an annual schedule, and stored in isolated key management vaults with strict multi-engineer quorum controls.
4. Multi-Tenant Data Isolation & Partitioning
Staff Scheduling serves organizations worldwide on a high-efficiency shared infrastructure. We enforce rigorous logical boundaries:
Mandatory Database Query Parameterization
SELECT * FROM time_entries WHERE business_id = :session_business_id AND id = :entry_id- Strict Session Scoping: The
business_idis derived exclusively from the authenticated server-validated session. Client attempts to pass arbitrary organization IDs in query strings are rejected. - Automated Boundary Guardrails: Backend middleware (
require_guard($pdo)) validates organization boundaries on every API request. Unauthorized access triggers an immediate403 Forbiddenand logs a security event.
5. Authentication, 2FA & Session Integrity
5.1 Password Hashing & Zero Plaintext Storage
Passwords are never stored in plaintext or reversible encryption. We use industry-standard Bcrypt (PASSWORD_DEFAULT) with high-cost salt parameters.
5.2 Two-Factor Authentication (MFA / 2FA)
- Authenticator App (TOTP): Compatible with Google Authenticator, Microsoft Authenticator, Authy, and 1Password.
- Email OTP: Generates a cryptographically random 6-digit numeric verification code with a strict 10-minute validity window, verified via constant-time string comparison (
hash_equals()). - Admin Enforcement: Organization owners can enforce mandatory 2FA for all managers and administrators.
5.3 Cryptographic Session Management
Session identifiers are generated with 256 bits of entropy (random_bytes(32)). Web session cookies enforce HttpOnly, Secure, and SameSite=Lax flags to eliminate client-side script theft.
5.4 Brute-Force Throttling & Rate Limiting
Our AuthRateLimitService monitors failed authentication attempts. Repeated failures trigger exponential backoff delays and temporary IP lockouts, returning HTTP 429 Too Many Requests. New-device sign-ins trigger an immediate asynchronous email alert.
6. Application Security & Defensive Engineering
- SQL Injection Immunization: 100% of database queries utilize PHP Data Objects (PDO) with parameterized prepared statements. String concatenation in SQL is strictly prohibited.
- Cross-Site Scripting (XSS) Defenses: All output rendered in browser contexts is encoded using
htmlspecialchars()withENT_QUOTES | ENT_SUBSTITUTEand UTF-8 encoding. - CSRF Token Validation: All state-changing POST/PUT requests require valid CSRF tokens verified via
hash_equals(). - Non-Webroot File Isolation: Time clock selfies are saved in private directories outside the web server root (
/storage/) and served exclusively through authenticated session proxy endpoints.
7. Role-Based Access Controls (RBAC)
Staff Scheduling enforces granular Role-Based Access Controls governing every view and action:
| Role Tier | Operational Boundaries & Data Access |
|---|---|
| Owner | Organization-wide governance, subscription billing, location management, and audit logs. |
| General Manager | Cross-branch scheduling, leave approval, and workforce analytics. Blocked from billing settings. |
| Manager | Scoped strictly to assigned physical location. Can publish shifts and inspect clock-in selfies only for local staff. |
| Supervisor | Shift-level supervision. Can view on-duty attendance and shift tasks. Blocked from viewing wage rates and payroll totals. |
| Employee | Self-service access strictly limited to personal shifts, timesheets, and task assignments. |
8. High Availability, Backups & Disaster Recovery
- 99.9% Uptime SLA: Distributed web application nodes and automated health checking.
- Automated Daily Backups: Daily relational database dumps and media snapshots encrypted with AES-256.
- Geographic Redundancy: Backups are replicated offsite to secondary disaster recovery regions.
- Recovery Point Objective (RPO): < 24 hours (maximum allowable theoretical data loss).
- Recovery Time Objective (RTO): < 4 hours (target duration to restore service from offsite cold storage).
9. Vulnerability Management & Responsible Disclosure
We welcome collaboration with ethical security researchers. If you identify a potential vulnerability:
Responsible Disclosure Channel
Email: operations@getstaffscheduling.ca
We acknowledge valid submissions within 48 business hours and do not pursue legal action against researchers acting in good faith.
10. Corporate Governance & Operational Security
- Background Checks: All personnel with administrative or codebase access undergo comprehensive background vetting.
- Endpoint Protection: Company workstations enforce full-disk encryption (FileVault/BitLocker) and hardware MFA.
- Zero Local Production Data: Engineers are strictly prohibited from downloading customer production databases or PII to local laptops.
- Annual Security Training: Mandatory annual security and privacy awareness curriculum for all team members.
11. Contact Our Security Office
For security inquiries, vulnerability reporting, vendor risk assessments, or customer assistance:
- Customer Support: support@getstaffscheduling.ca
- General Inquiries & Questions: hello@getstaffscheduling.ca
- Security, Legal & Compliance Office: operations@getstaffscheduling.ca
- Security Directorate: Staff Scheduling Information Security Team