Exploring Opportunities in Cybersecurity,Computing& Ethical Hacking.

TechCrushHQ avatar
TechCrush.pro
@TechCrushHQJul 8, 2026

The Spaces brought together host Favor Babari with practitioners Alima Laolo (cybersecurity analyst), Vivian Amaka Onya (cybersecurity engineer), Dare (Cloud & DevOps engineer), and Dixon Michael John (ethical hacking) to demystify career paths in cybersecurity, cloud computing, and ethical hacking. Speakers traced their non-linear entries into tech, stressing fundamentals (networking, operating systems, Linux), structured learning to counter information overload, and learning-by-doing via home labs and real projects. Alima recommended starting broad, then specializing (e.g., SOC/IR, threat intel, pen testing). Vivian reinforced building core IT knowledge, hands-on labs, and focusing on one domain before expanding. Dixon defined ethical hacking as authorized security testing, differentiated it from broader cybersecurity, and listed critical skills and tooling. Dare explained cloud computing concepts, provider choices (AWS vs Azure), shared-responsibility security, Well-Architected pillars, and modern practices like CLI, Terraform, Git, and CI/CD. The session closed with practical advice: research, mentorship, consistency, and perseverance—do it until you can’t miss it.

Exploring Opportunities in Cybersecurity, Cloud Computing, and Ethical Hacking — Beginner-to-Career Insights

Participants and Roles

  • Host: Favor Babari
  • Cybersecurity Analyst: Alima Laolo
  • Cybersecurity Engineer: Vivian Amaka Onya
  • Cloud/DevOps Engineer: Dare (Cloud & DevOps)
  • Ethical Hacking Specialist: Dixon Michael John

Session Overview

A roundtable focused on helping beginners make informed decisions about three tech tracks: cybersecurity, cloud computing, and ethical hacking. Speakers compared how they chose their paths, the fundamentals required, how to start effectively, when to specialize, and practical, hands-on approaches for building competence. Recurring themes included the importance of fundamentals, hands-on practice, personal research, structured learning paths, mentorship, and consistency.

Cybersecurity: Pathways, Fundamentals, and How to Start (Alima, Vivian)

Why Cybersecurity and What It Requires

  • Alima emphasized that you cannot secure what you do not understand. Security work demands a strong grasp of how infrastructure works (networks, systems, applications, cloud) before you can secure it. Her curiosity about how systems and new technologies (e.g., AI, IoT) work drew her into cybersecurity and incident response.
  • She highlighted that as technology evolves (AI, IoT, connected devices), security scope grows, increasing the need for ongoing research and learning.

Early Challenges and Lessons

  • Alima: Transitioned from web development and sampling multiple fields to cybersecurity. Faced isolation and information overload because security wasn’t common among peers initially. Self-learning and structured research were crucial. Over time, cloud, networking, and operations knowledge tied together into a coherent security path.
  • Vivian: Despite an IT background (networking, programming, databases), she initially faced directionlessness and information overload. She discovered cybersecurity is broader than “hacking”—it’s about protecting people, businesses, and critical systems. She gained experience across SOC operations, vulnerability management, pentesting, incident response, and risk assessment. The field requires continuous learning; fundamentals make advanced topics easier.

Generalist First or Early Specialization?

  • Alima recommends starting as a generalist: foundational networking, Linux terminal, and basic cybersecurity concepts before sampling specializations (e.g., vulnerability management, pentesting, threat intelligence) and then choosing one. Use a structured learning path to avoid information overload.

Practical Starting Advice (Beyond Tutorials)

  • Alima: Learn by doing (projects/labs) and cultivate personal research. Curiosity drives progress. New tech brings new attack surfaces—research how attackers might abuse them.
  • Vivian: Build a home lab and practice consistently. Suggested steps for beginners:
    • Operating systems: Learn Windows and Linux (comfortable with terminal, permissions, processes, services). Practice PowerShell and Command Prompt on Windows; Bash on Linux.
    • Virtualization/Lab: Use VirtualBox/VMware; install Windows Server (e.g., 2019/2022), Windows 10/11, and Linux (Kali/Parrot/Ubuntu). Practice Active Directory (forests, domains, domain joins), set up admin accounts, and break/fix scenarios.
    • Pentesting labs: Use Metasploitable and similar intentionally vulnerable VMs; practice manual exploitation and validation.
    • Platforms: TryHackMe (beginner-friendly) and Hack The Box (intermediate+) for structured learning and CTF practice.
    • Programming exposure: Gain at least a working understanding of front-end/back-end concepts; for mobile app testing, disassemble APK/IPA to analyze insecure code/logic.
    • Consistency over intensity: Even 1 hour daily beats cramming only on weekends. Don’t compare yourself to 10-year veterans—focus on steady improvement.

Ethical Hacking: Definition, Scope, and Getting Started (Dixon)

What Ethical Hacking Is—and Isn’t

  • Ethical hacking is the authorized testing of systems/networks/applications to find weaknesses before malicious actors exploit them. Authorization is the key boundary: without it, you cross into illegal activity (black/gray hat).
  • Typical activities: Web and app assessments, network defense testing, vulnerability identification, authentication/password evaluation, and responsible disclosure/reporting.

How It Fits Within Cybersecurity

  • Ethical hacking is a specialization within the broader cybersecurity field. Cybersecurity includes prevention, detection, response, recovery, governance, and compliance. Ethical hackers simulate attacker techniques (e.g., pentesting, red teaming) to improve defenses.

Foundational Knowledge and Tools for Beginners

  • Networking: TCP/IP, OSI model, DNS, routing, firewalls, VPNs.
  • Operating systems: Linux and Windows (file systems, permissions, services, processes). Linux fluency is foundational for hacking workflows.
  • Scripting/programming: Python, Bash (Linux), PowerShell (Windows), plus useful exposure to JavaScript and basic C.
  • Web technologies and security: Understand HTTP, sessions, cookies; learn common vulnerabilities (e.g., SQLi, XSS, CSRF, SSRF) and pentest methodology.
  • Security fundamentals: CIA triad (confidentiality, integrity, availability), risk management, cryptography, authentication.
  • Core tools: Wireshark, Nmap, Burp Suite, Metasploit, and others (learn how and when to use them, not just tool-clicking).
  • Broader exposure helps: Digital forensics basics, cloud security, containers/virtualization, secure coding principles.
  • Practical tip: Costs can be a challenge—plan for labs, courses, and tooling accordingly.

Cloud Computing: What It Is, Why It Matters, and How to Start (Dare)

What Cloud Computing Is—in Practical Terms

  • Think of a computer you control but don’t physically see: you choose the OS, CPU, memory, storage, and run apps via console/CLI/APIs. Providers host and maintain the physical infrastructure; you provision and manage what you need and pay for usage.
  • Organizationally, entire stacks move to the cloud: networking, compute, storage, and databases. Security remains central: the provider secures “of the cloud,” while you secure what you deploy “in the cloud” (patching, configuration, identity, data).

Deployment Models and Providers

  • Deployment models: On-premises, cloud-provider-managed, and hybrid (mix of on-prem and cloud provider).
  • Major providers: AWS, Microsoft Azure, Google Cloud (GCP), Oracle Cloud, IBM Cloud, among others. AWS has a large global market share; locally (e.g., Nigeria), Azure roles may be more prevalent—opt for what your job market commonly uses.

Cloud Fundamentals and Architecture

  • Core pillars/primitives: Identity and Access Management (IAM), storage, networking, compute, and databases.
  • Well-Architected pillars (illustrated via AWS): Operational excellence, security, reliability, cost optimization, performance efficiency. Cost awareness is critical—unused resources still incur fees.

Getting Started Effectively

  • Pick one platform first (often Azure in Nigeria due to demand; AWS globally popular). Avoid multi-cloud at the beginning.
  • Learn the provider’s console and then its command-line interface (CLI). Most real work is automated or scripted; direct console access may be restricted in professional environments.
  • Version control and collaboration: Git and a platform like GitHub/GitLab/Bitbucket.
  • Infrastructure as Code (IaC): Terraform is widely used to provision cloud resources without manual console work.
  • CI/CD (DevOps): Understand pipelines for build/test/security scans/deploys—deploy updates automatically as developers commit code.
  • OS and scripting: Solid Linux command-line skills and Bash scripting. Expect to work closely with developers—basic scripting helps bridge gaps.
  • Mindset: Start small, be consistent daily, and expect multiple failed attempts before success. Perseverance example: building a Bitbucket pipeline took 26 iterations before it worked end-to-end.

General Guidance for Beginners Across Tracks

Fundamentals First

  • Networking basics (TCP/IP, OSI, DNS, routing, firewalls/VPNs).
  • Operating systems (Windows and Linux) and command-line fluency.
  • Scripting/programming exposure (Python, Bash, PowerShell; optional JS/C for security tooling contexts).
  • Version control (Git) and documentation habits.

Start Broad, Then Specialize

  • Learn core concepts across your chosen domain (cybersecurity/cloud) and then sample a few specializations before committing deeply to one (e.g., SOC/IR, vulnerability management, pentesting, cloud security, DevOps/Platform Engineering).
  • Use a structured learning path to avoid information overload.

Hands-On, Research, and Consistency

  • Build and break labs; recreate tutorials and then modify them; pursue mini-projects that force you to diagnose and fix issues.
  • Practice on platforms (TryHackMe, Hack The Box) and document your learning.
  • Research proactively—new technology introduces new attack surfaces. Curiosity is a force multiplier.
  • Consistency beats perfection. Daily, focused practice outperforms sporadic cramming.

Mentorship, Community, and Market Awareness

  • Mentorship accelerates progress and helps avoid common mistakes.
  • Communities provide support, accountability, and opportunities.
  • Align learning with local job market realities (e.g., Azure roles may be more common in certain regions).

What the Speakers Would Tell Their Earlier Selves

  • Dare:
    • Start small and don’t rush. Keep going after you “get it”—practice until you can’t miss.
    • Hands-on persistence matters more than theory. You learn by trying, failing, and iterating.
  • Vivian:
    • Master fundamentals first (networking, OS, how computers communicate) before advanced topics.
    • Focus on one path initially instead of learning everything at once; become proficient, then expand.
    • Prioritize hands-on projects and labs over collecting certifications alone.
    • Find mentors and build a professional network early; be patient and avoid unhealthy comparisons.
  • Alima: Emphasized earlier throughout the session the value of foundational breadth before specialization, hands-on practice, structured learning, and continuous research; the “advice to earlier self” segment wasn’t captured due to network issues.

Highlights and Memorable Takeaways

  • “You cannot secure what you don’t understand.” — Know systems before securing them.
  • Learn by doing; research continuously; curiosity is essential.
  • Start as a generalist, then specialize with a structured plan.
  • Consistency > perfection: even one focused hour daily compounds.
  • Cloud security is shared responsibility; IAM is the pillar.
  • Costs matter in cloud—design for cost optimization from day one.
  • Ethical hacking is authorized testing; without permission, it’s illegal.
  • Local context matters when choosing a cloud provider to start with.
  • Implementation is more important than consumption—act on what you learn.

Actionable Next Steps (Beginner Roadmaps)

  • Common core (all tracks):
    • Week 1–4: Daily 45–60 minutes on TCP/IP, OSI, DNS; install Linux (Ubuntu), learn basic Bash; practice Windows command line and PowerShell; set up Git and push a README documenting your learning plan.
    • Week 5–8: Build a home lab (VirtualBox/VMware). Add Windows Server + AD, Windows 10/11 client, and a Linux server. Practice domain joins, user/group policies, and basic services.
  • Cybersecurity (defensive/SOC/IR):
    • Learn log fundamentals and common telemetry; simulate incidents in your lab.
    • Document small incident response playbooks and practice them in your environment.
  • Pentesting/Ethical hacking:
    • Install Kali/Parrot; practice with Metasploitable/OWASP Juice Shop.
    • Learn OWASP Top 10 and Burp Suite workflows; escalate from TryHackMe to Hack The Box.
    • Write short reports for your lab findings (screenshots, commands, remediation).
  • Cloud/DevOps:
    • Choose one provider (Azure or AWS). Learn console then CLI. Build a VPC/VNet, a VM, and secure with IAM.
    • Learn Terraform to provision the same setup as code; store code in Git; build a basic CI pipeline (GitHub Actions/Bitbucket Pipelines) to validate and apply infra changes.
    • Track costs and tear down resources when done.

Closing Notes

The session reinforced that success in cybersecurity, cloud computing, and ethical hacking depends on fundamentals, hands-on practice, structured learning, research, mentorship, and consistency. The host reminded attendees to act on what they learned, monitor scholarship communications, and use these insights to make informed decisions about which path—cybersecurity, cloud, or ethical hacking—best fits their goals and context.