Security Policy

How we protect your data, your account, and our platform

🔒

TLS 1.2+ Everywhere

All data encrypted in transit; HTTPS enforced sitewide

🛡️

bcrypt + Argon2

Industry-standard password hashing with high cost factors

🔑

JWT + Secure Rotation

Short-lived tokens with automatic rotation and revocation

🏗️

SOC 2 Infrastructure

Hosted in certified data centres with DDoS protection

🔍

Continuous Scanning

Automated vulnerability scanning and dependency audits

👥

Zero-Trust Access

Least-privilege access; MFA required for all admin systems

1. Infrastructure Security

  • Hosting: Proflynk's production infrastructure is hosted on cloud providers with SOC 2 Type II and ISO 27001 certifications. Data centres are physically secured with biometric access, 24/7 CCTV, and redundant power.
  • HTTPS enforcement: All web and API traffic is served over HTTPS. HTTP requests are automatically redirected. HSTS (HTTP Strict Transport Security) with a long max-age is enforced on all domains.
  • TLS configuration: TLS 1.2 and 1.3 only. Weak ciphers (RC4, 3DES, export-grade) and deprecated TLS 1.0/1.1 are disabled.
  • Network isolation: Production, staging and development environments are fully isolated in separate network segments. Database servers are not publicly accessible; access is restricted to application servers via private networking.
  • DDoS protection: Layer 3/4 and Layer 7 DDoS mitigation is in place. Rate limiting and traffic scrubbing protect against volumetric and application-layer attacks.
  • Backups: Automated daily backups with point-in-time recovery. Backups are encrypted at rest and stored in a geographically separate region. Restoration is tested regularly.
  • Uptime monitoring: 24/7 automated monitoring with alerting. Status updates are published at status.proflynk.com.

2. Application Security

  • OWASP Top 10: Our development processes incorporate mitigations for all OWASP Top 10 vulnerabilities. Regular security training is mandatory for all engineers.
  • SQL injection prevention: All database queries use parameterised queries/prepared statements. No raw SQL string concatenation with user-controlled input is permitted in our codebase.
  • XSS prevention: Output encoding is applied universally. Content Security Policy (CSP) headers restrict script execution. React's DOM escaping is used throughout the frontend.
  • CSRF protection: Cross-site request forgery protection is enforced on all state-changing API endpoints.
  • Authentication: JSON Web Tokens (JWT) with short expiry (access tokens: 15 minutes; refresh tokens: 7 days). Tokens are cryptographically signed and validated on every request.
  • Rate limiting: Rate limiting is applied on authentication endpoints, password reset flows, API endpoints and all public-facing forms to prevent brute-force and abuse.
  • Dependency management: Automated dependency audits run on every code push. Known vulnerabilities in dependencies trigger alerts and are patched within our SLA (critical: 24 hours; high: 7 days).
  • Secure development lifecycle: Security review is a mandatory step in our pull-request process. Secrets must not be committed to version control — automated scanning blocks this.
  • Content Security Policy: Strict CSP headers are set on all pages. Inline scripts and eval are blocked. Only approved CDNs may serve third-party scripts.

3. Data Encryption

  • In transit: All data transmitted between users' browsers/apps and Proflynk's servers is encrypted using TLS 1.2 or 1.3 with strong cipher suites (AES-256-GCM preferred).
  • At rest: All databases, storage volumes and backups are encrypted at rest using AES-256 encryption. Encryption keys are managed through a dedicated key management service (KMS) with key rotation policies.
  • Passwords: Passwords are hashed using bcrypt (minimum cost factor 12) or Argon2id. Plain-text passwords are never stored or logged.
  • Payment data: Card details are handled directly by our PCI-DSS Level 1 certified payment processor. Proflynk stores only a tokenised payment reference — never raw card numbers, CVVs or expiry dates.
  • Sensitive fields: Particularly sensitive data fields (e.g. verification document results, authentication tokens) are encrypted at the application layer in addition to storage-level encryption.

4. AI System Security

Our AI features introduce specific security considerations that we address as follows:

  • Prompt injection prevention: AI features that accept user input are protected against prompt injection attacks through input validation, sandboxing and output validation.
  • Model access controls: AI model endpoints are authenticated and rate-limited. Models are not exposed directly to end users.
  • Training data privacy: AI models are trained on anonymised and pseudonymised data. Individual user data is not used for model training without explicit consent.
  • AI output labelling: All AI-generated content, scores and recommendations are clearly labelled as AI-generated on the platform. Users are not misled into believing AI outputs are human judgments.
  • Adversarial robustness: We test our AI models for adversarial inputs and monitor for unusual patterns that may indicate misuse.

5. Account Security (Users)

We provide users with tools to protect their own accounts:

  • Two-factor authentication (2FA): Available for all accounts via authenticator app (TOTP). Strongly recommended and mandatory for recruiter and admin accounts. Enable in Settings → Security → Two-Factor Authentication.
  • Password requirements: Minimum 8 characters. We encourage the use of a password manager and long, unique passphrases.
  • Breach detection: Passwords are checked against known-compromised password databases (Have I Been Pwned / k-anonymity model) at account creation and login.
  • Active session management: View and revoke all active sessions in Settings → Security → Active Sessions.
  • Login notifications: You will be notified by email of logins from new devices or unusual locations.
  • Account lockout: Accounts are temporarily locked after repeated failed login attempts to protect against brute-force attacks.
  • Secure email verification: New accounts and email changes require email verification via a time-limited token.

6. Access Controls

  • Role-based access control (RBAC): All platform access is governed by RBAC at the API layer. Users, recruiters, company admins, and system administrators have distinct permission scopes.
  • Principle of least privilege: Staff are granted only the minimum access required for their role. Access is reviewed quarterly and promptly revoked on offboarding.
  • Zero-trust architecture: Internal services authenticate to each other; no service trusts requests solely because they originate from inside the network perimeter.
  • Multi-factor authentication: MFA is mandatory for all Proflynk employees accessing production systems, internal admin tools, and third-party services with access to customer data.
  • Privileged access management: Privileged access (e.g. database direct access, infrastructure changes) requires just-in-time approval and is fully logged and auditable.
  • Audit logging: All significant internal and administrative actions are recorded in immutable audit logs retained for 12 months.

7. Third-Party & Supply Chain Security

  • Third-party vendors with access to customer data are subject to security due diligence before onboarding, including review of their security certifications and practices.
  • All sub-processors are contractually bound to maintain security standards equivalent to or exceeding our own. See our GDPR page Section 10 for sub-processor details.
  • Open-source software dependencies are tracked via a software bill of materials (SBOM) and monitored for published vulnerabilities.
  • Third-party scripts loaded on the platform are reviewed and subject to Subresource Integrity (SRI) verification where applicable.

8. Security Assessments & Compliance

✓ Penetration Testing

Annual third-party penetration tests covering web application, API, and infrastructure layers. Critical findings are remediated within 24 hours.

✓ Vulnerability Scanning

Automated DAST (Dynamic Application Security Testing) and SAST (Static Analysis) integrated into our CI/CD pipeline. Every code change is scanned.

✓ Dependency Auditing

Continuous monitoring for known vulnerabilities in third-party libraries via automated tools. Patch SLA: critical 24h, high 7 days.

✓ GDPR Compliance

Full GDPR compliance programme including DPIAs, breach notification procedures, and a DPA for B2B customers. See our GDPR page.

✓ ISO 27001 Principles

Our security management programme follows ISO 27001 principles for information security management systems (ISMS).

✓ OWASP Top 10

Mitigations for all current OWASP Top 10 vulnerabilities are implemented and verified in annual assessments.

9. Vulnerability Disclosure Programme

We operate a responsible vulnerability disclosure programme (VDP). Security researchers who discover vulnerabilities affecting Proflynk's systems or users are invited to report them to us in accordance with this programme.

How to report

Send your report to [email protected]. PGP encryption is available on request. Please include:

  • A clear description of the vulnerability and its impact
  • Step-by-step reproduction instructions
  • Proof-of-concept (screenshots, HTTP requests) where possible
  • Your assessment of the CVSS severity
  • Your name/handle (for acknowledgement, if desired)

Our commitments

  • We will acknowledge your report within 48 hours
  • We will confirm whether the report is in scope within 5 business days
  • We will work diligently to resolve confirmed vulnerabilities and keep you informed of progress
  • We will credit you in our Security Hall of Fame for responsible disclosures (unless you prefer anonymity)
  • We ask that you do not publicly disclose the vulnerability until a fix has been deployed and 30 days have passed, or until we agree on a coordinated disclosure timeline

Out of scope

  • Denial of Service (DoS/DDoS) attacks
  • Social engineering of Proflynk employees
  • Physical attacks on data centres
  • Automated scanning without prior written permission
  • Vulnerabilities in third-party services not under Proflynk's control

Safe Harbour

Proflynk will not pursue legal action against researchers who discover and responsibly disclose vulnerabilities in accordance with this programme, provided they do not access or modify user data, disrupt the platform or its users, or violate applicable law.

10. Incident Response

Proflynk maintains a formal Incident Response Plan (IRP) with the following key elements:

  • Detection: 24/7 automated monitoring and alerting covers infrastructure anomalies, authentication failures, unusual data access patterns, and security events.
  • Triage: Security incidents are classified by severity (Critical / High / Medium / Low) with defined response SLAs.
  • Containment & Eradication: Defined playbooks for common incident types. Compromised credentials are revoked immediately; affected systems are isolated pending investigation.
  • Notification: Personal data breaches that meet GDPR or applicable law notification thresholds will be reported to supervisory authorities within 72 hours and to affected users without undue delay. See GDPR Section 13.
  • Post-incident review: All significant incidents are subject to a blameless post-mortem. Findings drive improvements to prevent recurrence.

11. Business Continuity & Disaster Recovery

  • Proflynk maintains a Business Continuity Plan (BCP) and Disaster Recovery Plan (DRP), reviewed and tested annually.
  • Recovery Time Objective (RTO): 4 hours for critical services; Recovery Point Objective (RPO): 1 hour (time to last good backup).
  • Multi-region architecture provides geographic redundancy for critical services.
  • Backup restoration is tested quarterly to verify data integrity and recovery procedures.

12. Contact

Security Vulnerabilities

Report security issues responsibly:

[email protected]

Account Security Issues

Compromised accounts or suspicious activity:

[email protected]

Data Protection

Privacy and GDPR enquiries:

[email protected]

Enterprise Security

Security questionnaires and enterprise assessments:

[email protected]