Security & Responsible Disclosure

Effective Date: November 13, 2026 · Last Updated: November 2026

Devwalls is dedicated to cultivating the highest standards of security engineering and ethical conduct. This document outlines our Ethical Hacking Commitment, Laboratory Sandbox Isolation, and Responsible Disclosure Safe Harbor program.

Student Ethical Pledge

1. The Devwalls Ethical Hacker Pledge

Every student and practitioner enrolled in Devwalls Academy must uphold our core ethical principles. Knowledge acquired in our offensive and AI security rooms carries real-world responsibility:

  • Authorization First: Never perform scans, penetration tests, or security audits without explicit, written permission from the asset owner.
  • Do No Harm: Never destroy data, disrupt production services, exfiltrate sensitive customer records, or install persistence backdoors outside authorized scopes.
  • Defend the Ecosystem: Use your technical capabilities to fortify African and global software infrastructure against criminal syndicates.

2. Isolated Laboratory Sandbox Architecture

Devwalls Academy runs an isolated sandbox infrastructure to let students practice real vulnerabilities safely:

Containerized Ephemeral Targets

Target environments (vulnerable web applications, APIs, network services) run in transient network namespaces without outbound public Internet egress.

Strict Lateral Movement Barriers

Student lab sessions are isolated from one another. A compromise of a target container cannot pivot or compromise adjacent student workspaces.

3. Responsible Disclosure Safe Harbor

If you believe you have identified a vulnerability in the Devwalls Academy web application, authentication system, or production infrastructure, we welcome your disclosure under our Safe Harbor commitment:

  • We will not initiate legal action against security researchers who comply with our disclosure policy and act in good faith.
  • We commit to acknowledging received vulnerability reports within 48 hours.
  • We will provide status updates as triage and remediation progress toward deployment.

4. How to Report a Vulnerability

Please submit your findings via encrypted email to our security team. Include clear steps to reproduce, affected endpoints, and evidence (proof of concept code, HTTP requests):

Email: security@devwalls.com

PGP Fingerprint: 84F2 9A10 3DE1 C502 B911 2049 E81A 447D

Response SLA: < 48 hours