Frequently Asked Questions

Our educational philosophy focuses on practice-led technical competence rather than theoretical rote memorization. We combine concept breakdowns with hands-on lab exercises and realistic investigation capstones so learners develop operational fluency with genuine security tools, authentic telemetry, and evidence documentation standards.

No. The academy is an independent specialised technical training initiative. We do not claim university accreditation, formal degree-granting status, or state licensing. Our courses are designed around documented industry practices and verifiable portfolio deliverables.

The academy operates as a virtual instruction programme. We do not maintain physical classroom facilities or dedicated physical hardware labs. All hands-on practice is conducted on learner workstations using virtualized environments (VirtualBox, VMware, UTM) or cloud evaluation platforms.

If you are new to cybersecurity operations, the SOC Analyst pathway (8 weeks) is the recommended entry point. If you are focused on vulnerability assessment and offensive security, choose Ethical Hacking (10 weeks). For cloud architecture and Microsoft Sentinel detection engineering, select Azure Cloud Security (10 weeks). If your interest lies in forensic disk/memory analysis and post-breach investigation, select Digital Forensics & Incident Response (DFIR) (10 weeks).

SOC operations focus on real-time and near-real-time alert monitoring, initial triage, SIEM query tuning, and immediate containment. DFIR focuses on deep retrospective analysis: preserving cryptographic integrity, mounting disk images in Autopsy, parsing volatile RAM dumps with Volatility 3, and reconstructing minute-by-minute forensic timelines.

We recommend taking one pathway at a time. Each course entails 8 to 10 weeks of rigorous study comprising 64 to 80 guided learning hours plus substantial independent hands-on lab time. Focusing on a single track ensures you can dedicate sufficient attention to the 40% capstone project.

All pathways require solid computer literacy, basic operating system navigation (Windows and Linux terminal basics), and foundational networking concepts (IP addressing, TCP/UDP, DNS, HTTP). Prior programming experience is helpful but not strictly required, as scripts are introduced incrementally through guided exercises.

The SOC Analyst course is structured specifically for beginner-to-intermediate learners and introduces security operations from foundational principles. Specialised courses (Ethical Hacking, Azure Cloud Security, and DFIR) assume familiarity with fundamental networking and systems architecture.

Durations are verified against the official course syllabi:
• SOC Analyst: 8 Weeks (64 guided learning hours).
• Ethical Hacking & Penetration Testing: 10 Weeks (80 guided learning hours).
• Azure Cloud Security Engineer: 10 Weeks (80 guided learning hours).
• Digital Forensics & Incident Response (DFIR): 10 Weeks (80 guided learning hours).

Delivery formats (including live cohort session times, time zones, recording availability, and weekly cohort cadence) are currently unconfirmed. We do not provide estimated class timetables prior to client scheduling confirmation.

Instruction across all four courses is heavily biased toward practical execution. Under the suggested assessment model, 30% of total evaluation is dedicated to guided practical lab exercises and 40% to the comprehensive final capstone project. Traditional knowledge checks and quizzes account for only 10% of grading.

Modules follow a scaffolded progression: starting with foundational architecture, protocol analysis, and log telemetry, then moving into intermediate analysis and triage worksheets, and culminating in realistic multi-stage scenarios (such as enterprise ransomware defence or authorized external penetration testing).

Tooling is derived strictly from Table 1 of each official syllabus:
• SOC: Wazuh, introductory Splunk, Wireshark, Windows Event Viewer, Sysmon, PowerShell, Linux CLI.
• Pentest: Kali Linux, Nmap, Nessus/OpenVAS, Burp Suite, OWASP ZAP, Metasploit.
• Azure: Microsoft Entra ID, Azure RBAC, PIM, NSGs, Key Vault, Defender for Cloud, Microsoft Sentinel, KQL.
• DFIR: Autopsy, The Sleuth Kit, Registry Explorer, Volatility 3, Wireshark, SHA-256 utilities.

No. The academy does not provide paid enterprise commercial licenses or dedicated cloud tenant subscriptions. Training utilizes open-source tools, free community workflows, curated training datasets, and learner-provisioned evaluation accounts (such as Azure free trial or student tiers).

General Operational Recommendation (Not an official syllabus requirement): The official course documents do not specify mandatory CPU architectures or RAM minimums beyond noting that equivalent tooling or datasets can be substituted where hardware constraints apply. For learners running local hypervisors (VirtualBox, VMware, or UTM) with virtual machines, general industry practice recommends a 64-bit operating system with hardware virtualization enabled (VT-x/AMD-V), a multi-core processor, 8–16 GB of RAM, and 50+ GB of free storage.

All four courses utilize the following suggested assessment structure:
• 10% Knowledge Checks & Quizzes: Conceptual verification.
• 30% Guided Practical Labs: Tool operation and technical exercises.
• 20% Written Triage Reports: Technical writeups and investigation worksheets.
• 40% Final Course Capstone: Comprehensive simulation and investigation report.

The capstone is an authentic multi-stage scenario evaluated at the end of each course. Rather than a multiple-choice exam, learners analyse a simulated incident or perform an authorized security assessment, producing an evidence-based technical report complete with event timelines, impact assessments, and prioritized remediation guidance.

The course proposals suggest an overall 70% minimum passing score, which includes satisfactory completion of practical labs and submission of the final capstone project. Note: This passing threshold is currently a proposal and requires final client confirmation prior to formal cohort opening.

Certificate policies, digital badge verification standards, and credential criteria are currently unconfirmed and subject to formal academy governance approval.

Tuition fees, payment schedules, and institutional funding options are currently unconfirmed and under institutional review. We do not publish speculative fees. Prospective learners may review the published course syllabi for technical requirements.

All four course pathways, weekly module breakdowns, and guided lab requirements are fully published and accessible directly on this website. When formal cohort schedules are confirmed, updates will be announced on the respective course pages.

No. We strictly refuse to make unrealistic job placement promises, recruiter quotas, or employment guarantees. Hiring in cybersecurity depends on macroeconomic conditions, employer requirements, and individual competence. Our objective is providing authentic technical instruction and portfolio artifacts that demonstrate verifiable problem-solving skills.

Career support initiatives—including capstone report reviews, resume formatting guidance for technical coursework, and technical interview preparation workshops—are currently under development and awaiting formal client confirmation. For detailed self-guided advice, review our Career Development Guide.