Security

Secure by design. Secure by default.

Security decisions are made at the start of a project, checked during development and tested before release. OWASP guidance is our working reference throughout.

No web application can honestly be guaranteed 100% secure. We reduce risk, document what remains and keep improving.

Principles

  • 01

    Secure by design

    Threat modelling and security requirements are part of architecture.

  • 02

    Secure by default

    Safe configuration from the first deploy; risky features are opt-in.

  • 03

    Least privilege

    Users, services and keys receive only the access they need.

  • 04

    Defense in depth

    Independent layers so one failure does not expose the system.

  • 05

    Input validation

    All input is untrusted and validated on the server against allow-lists.

  • 06

    Output encoding

    Context-aware encoding to prevent injection and XSS.

  • 07

    Minimal attack surface

    No features, endpoints or packages that are not needed.

  • 08

    Dependency security

    Pinned versions, regular audits and prompt updates.

  • 09

    Security testing

    Code review and testing before major releases.

  • 10

    Continuous improvement

    Findings feed back into standards and checklists.

How we address common risk categories

Categories from the OWASP Top 10. We follow the latest published edition and related OWASP projects (ASVS, API Security Top 10, Top 10 for LLM Applications) where relevant.

Broken access control

Authorization enforced on the server for every request and object; deny by default; tests for IDOR and privilege escalation.

Cryptographic failures

TLS everywhere, HSTS, modern algorithms from maintained libraries, and secrets kept out of code.

Injection

Parameterised queries, ORM safeguards, schema validation and context-aware output encoding.

Insecure design

Threat modelling, abuse cases and business-logic review during architecture.

Security misconfiguration

Hardened defaults, security headers, no debug output or stack traces in production.

Vulnerable and outdated components

Dependency audits in CI, pinned versions and removal of unused packages.

Identification and authentication failures

Proven auth libraries, MFA support, secure session handling and rate-limited login.

Software and data integrity failures

Lockfiles, signed releases, protected CI/CD and verified third-party scripts.

Security logging and monitoring failures

Logging of security events without sensitive data, with alerting on anomalies.

Server-side request forgery

Allow-listed outbound destinations and validation of user-supplied URLs.

This website

We apply the same standards to devsecplus.com.

  • No user accounts, database or file uploads on the public site.
  • Form submissions are validated on the server, rate-limited and checked for spam.
  • Content-Security-Policy, HSTS, Referrer-Policy, Permissions-Policy and frame protection headers.
  • No advertising trackers. Privacy-conscious analytics only, if enabled.
  • Dependencies pinned and audited before each release.

Report a vulnerability

If you believe you have found a security issue in a DevSecPlus website or service, email us with a description and steps to reproduce. Please do not access other users' data, disrupt services or disclose publicly before we have responded.

contact@devsecplus.comSubject line: Security report