Agreement and scope
Before touching any system: signed contract, clear scope of which domains and applications are in, time window and rules of engagement. Without this, nothing happens.
SixHack Academy is an ethical hacking academy built around real practice. We don't teach how to "attack" systems: we teach how to audit them under authorization, report vulnerabilities professionally and operate within the legal framework that defines the profession.
Ethical hacking is the practice of identifying and exploiting vulnerabilities in systems with explicit permission from the owner, with the goal of reporting them so they can be fixed. Technically, the tools and methods are the same a malicious attacker would use. What changes β significantly β is the legal context and the intent.
An ethical hacker always operates within three frames: a written authorization (audit contract, public bug bounty program or owned system), a clear scope of what can and can't be touched, and a responsible disclosure process for what's found. Skipping any of the three turns the activity into a crime, even if the technique is identical.
That's why a real ethical hacking academy doesn't just teach techniques: it teaches the framework that makes them legitimate. At SixHack Academy all the content is delivered with that lens from the very first lab, because without that framework technical training doesn't prepare you to work professionally β it just gets you into trouble.
What matters isn't "ethical" intent, but authorization and scope.
Yes, it's legal when practiced on your own systems, in controlled labs or on third-party systems with explicit authorization and within the permitted scope. Spain ratified the Council of Europe Convention on Cybercrime (Budapest Convention), and the Spanish Criminal Code (CΓ³digo Penal) penalizes unauthorized access, interception, damage, alteration or interruption of third-party systems and data.
Specifically, article 197 bis covers unauthorized access to information systems and the unauthorized interception of non-public communications; articles 264 and 264 bis penalize computer damage and the serious obstruction of third-party information systems. Articles 197 ter and 264 ter also penalize the production or facilitation of tools and credentials with the purpose of committing those offenses β what matters here is the purpose and context, not the use of tools in training environments.
In practice, owned environments, contracted audits or bug bounty programs can be legal provided the rules are respected: in-scope domains, authorized techniques, no exfiltration of unnecessary data, no service disruption, no persistent access. Going out of scope, affecting non-included systems or exceeding the agreed limits can lead to criminal, civil or contractual liability β regardless of the researcher's intent.
At SixHack Academy all labs are hosted in isolated environments built specifically for you to learn. Every time you launch a challenge, that instance is yours. Working inside the platform is in the safe zone: you learn real techniques without touching third-party systems or operating outside authorization, and that's exactly the best preparation to operate with judgment later in the real world.
This is general information referring to the legal framework in Spain. It does not constitute legal advice. For specific cases, consult a qualified legal professional. If you operate from a different jurisdiction, the applicable rules may differ.
The full professional cycle, not just "find the bug".
Before touching any system: signed contract, clear scope of which domains and applications are in, time window and rules of engagement. Without this, nothing happens.
Mapping the attack surface within scope: subdomains, technologies, endpoints, application logic. Methodical work, not random.
Detecting real vulnerabilities (not false positives), exploiting them to confirm impact, capturing reproducible evidence. The whole OWASP Top 10 lives here.
Evaluating what each finding lets you do: scope of compromise, exposed data, business risk. Prioritizing by real severity, not by textbook listing.
Reporting professionally to the affected team, giving reasonable time to fix, validating the patch when ready. Only after that do you consider publishing details.
Professional deliverable with executive summary, detailed findings, reproducible evidence and remediation recommendations. The visible face of the ethical hacker's work.
The real options in the market. Not all of them go through traditional employment.
How to start working as an ethical hacker without a formal job.
A bug bounty program is a public initiative through which a company authorizes ethical hackers to look for vulnerabilities in their systems in exchange for a reward per valid finding. It's the most direct way to start working as an ethical hacker without needing an employment contract: you read the program, study the rules, start hunting and, if you find something, you report it and get paid.
The most well-known platforms are HackerOne, Bugcrowd, Intigriti and YesWeHack. Each one hosts programs from hundreds of companies with different scopes and reward tables. Some programs reward $50 per medium bug; others pay up to $100,000 for critical vulnerabilities in critical infrastructure.
To operate professionally in bug bounty you need judgment: knowing how to read a scope, understanding what's in and out, mastering the techniques (especially OWASP Top 10 if you're going for web), and above all knowing how to report. A good report multiplies the reward; a bad one shrinks it or kills it. We teach that in the WXJ track from day one.
Three progressive courses to train as an ethical hacker from scratch.
The entry point to ethical hacking. Assumes zero experience. Covers networking, HTTP/HTTPS, Burp Suite, OWASP Top 10 and real vulnerabilities (SQLi, XSS, IDOR, SSRF). Ethical framework and professional reporting from the first lab.
Continuation of WXJ. Advanced techniques, complex vulnerability chains and realistic professional auditing scenarios. For those with a foundation who want to operate at mid-level pentester or to add quality reports in bug bounty.
Ethical hacking applied to the mobile ecosystem. Static and dynamic analysis, common flaws and platform-specific exploitation techniques on Android and iOS. Complements the web track opening mobile bug bounty and app pentesting.
In the industry there are three usual ways to acredit work and experience: published CVEs (vulnerabilities with officially recognized identifier), Hall of Fame mentions from companies you've reported to, and training certifications. The three combine to build a verifiable technical profile.
SixHack Academy delivers its own certification with a unique identifier publicly verifiable via QR and token at cert.sixhackacademy.com. That lets you prove your level to recruiters and companies with a direct, verifiable link β no third-party dependency.
Before signing up for any course, you can train for free with our CTF Labs: real web hacking challenges with multiple difficulty levels, global ranking and free access after a quick sign-up. A direct way to check the methodology before investing.
SQL injection, XSS, IDOR, SSRF and other OWASP techniques in a fully legal environment.
The most common questions about legality, profession and training.
WXJ is the entry point: technique, legal framework and professional reporting from day one.