Exploring Cybersecurity, Cloud Computing and Ethical Hacking Careers

The Spaces brought together Abisola (host), Halima (cybersecurity analyst and instructor), Kenneth (ethical hacker), Yuxiao (cloud/DevOps engineer), and John (cloud/DevOps engineer) to demystify cybersecurity, ethical hacking, cloud computing, and DevOps careers. Halima emphasized transferable skills, dedication, fundamentals (Linux, networking, threat concepts), rapid learning, tool fluency, and the critical importance of reporting and presentation. She outlined common beginner pitfalls: rushing multiple courses, learning alone, using the wrong tools, and lacking curiosity. Kenneth described ethical hacking as authorized security testing with a structured scope, stressed starting from fundamentals, specializing (web, mobile, API, IoT/OT), and mastering report writing. Yuxiao clarified cloud vs DevOps responsibilities, the need to understand infrastructure, networking, security, automation, and advised mastering one cloud provider (AWS/Azure/GCP) because knowledge transfers. He shared a challenging Azure support role, perseverance, and career benefits (job security, pay, age-agnostic advancement, networking). John urged avoiding “shiny-object” learning, mastering basics (Linux, scripting, Git), and highlighted how small architectural choices (e.g., Kubernetes vs Cloud Run) carry major cost and reliability consequences. Q&A covered mentorship structure, programming needs in cybersecurity (useful later), daily habits (stay current, collaborate), tools, application timelines, and track switching.

Webinar Recap: Breaking into Cybersecurity, Ethical Hacking, Cloud & DevOps

Who spoke and their roles

• Host: Abisola (moderator/organizer)
• Halima — Cybersecurity Analyst and Instructor (≈9 years in tech; B.Sc. in Cybersecurity)
• John — Cloud and DevOps Engineer (≈6 years; started as System Administrator)
• Kenneth — Ethical Hacker (Penetration Tester) (≈7–8 years)
• Yuxiao — DevOps/Cloud Engineer (works with a US organization; transitioned from teaching into cloud, then DevOps)

Overview and intent of the session

• Audience: Applicants and beginners exploring Cybersecurity, Ethical Hacking, Cloud Computing, and DevOps.
• Goals: Demystify each path, go beyond the purely technical narrative, and surface what day-to-day work looks like, the mindset and habits required, common pitfalls, and practical entry strategies.
• Program context: The bootcamp offers live, mentor-led learning; a post-bootcamp alumni community; and periodic mentorship sessions. Applications close imminently; selection is next week. There will be a window to switch tracks announced in the community.

Cybersecurity: Pathways, demands, and day-to-day (Halima)

Halima’s path into cybersecurity

• Entered university intending to study Computer Science after working as a web developer/instructor; was transferred to Cybersecurity and leaned in.
• Sought mentors and online guidance when local guidance was scarce; leveraged transferable skills from web development (though not a prerequisite) to get started.

What “being a cybersecurity professional” really means

• Fast learning is essential: You must understand how a system/technology works before you can secure it. Expect rapid upskilling to become a subject matter expert on new tools/technologies within days to a couple of weeks.
  • Example: With the rise of AI video creation, a security analyst learns the tooling and underlying data flows to protect data confidentiality and integrity.
  • IoT example: Consumer “smart home” prompts are, in security terms, IoT systems; analysts must understand their architecture to design controls.
• Non-technical-but-critical work: Documentation, reporting, and presentation.
  • Every activity should be documented clearly so non-technical stakeholders understand the business impact, outcomes, and recommendations.
  • Presentations must avoid jargon yet convey risk, impact, and continuity objectives (security serves business continuity and data protection).

Transferable skills that map well

• Governance, Risk, and Compliance (GRC): Process definition, policy writing, and playbooks (SOPs) align with operations and incident workflows.
• Documentation and administration backgrounds (e.g., law/administration) ease into GRC and operational playbooks.
• Attention to detail: Vital for triaging alerts, threat intel, and investigations where small indicators can be decisive.
• Client-facing/communication: Crucial for presales/security engineering and stakeholder engagement (explaining risk to non-technical audiences).

Core foundations for beginners

• Concepts: Threats, vulnerabilities, defense-in-depth, and security operations basics.
• Platforms/skills: Linux fundamentals, networking basics, intro to cybersecurity and threat intelligence; understand system internals before applying controls.

Common beginner mistakes and how to avoid them

• Doing too much at once: Taking multiple courses simultaneously leads to shallow understanding. Follow a structured sequence; build layer by layer.
• Learning in isolation: Cybersecurity is team-centric. Collaborate on group tasks; exchange ideas and approaches.
• Using the wrong tools: A proper laptop/desktop is non-negotiable for enterprise security tooling; learning on a phone will stall progress.
• Lack of curiosity and currency: Track daily security news and breach write-ups. Discuss incidents with peers/tutors; this builds professional thinking and readies you for interviews.

Ethical Hacking (Penetration Testing): Role, mindset, and entry (Kenneth)

Kenneth’s path and definition

• Started as a web developer (Computer Science graduate). A bank placed him in Information Security; learned on the job from colleagues.
• Ethical hacking means testing systems with explicit authorization to identify and report vulnerabilities. It’s methodical, scoped, and governed by contracts and rules of engagement.

Early challenges and lessons

• Overwhelmed by jargon and operations (firewalls, port scans, permissions) and the speed of live environments.
• Advice: Don’t skip foundations; understand the “why” and “how” behind exploits, not just the steps.

Focus and specialization

• Cybersecurity is vast; so is hacking. Common domains include web apps, mobile, APIs, IoT/OT, and networks.
• Pick a lane initially (e.g., web app security) to avoid confusion and build depth before expanding.

Soft skills and reporting

• Reporting is the hard, time-consuming part many overlook. It’s how value is communicated to stakeholders and how work is judged.
• Clear, actionable, business-aware reports are as important as the technical exploit.

Certifications and structured learning

• Employers value recognized certifications alongside hands-on skill. Structured bootcamps signal teachability and guided practice.
• Strong fundamentals are mandatory: Networking (DNS, TCP three-way handshake), protocols, and system internals—“You can’t hack or secure what you don’t understand.”

Typical engagement workflow

• Obtain written authorization and scope; define allowed tests and constraints (e.g., no Denial of Service).
• Recon and application understanding (flows, authentication, payments, data paths), then targeted testing where impact is likely.

Who can pursue ethical hacking?

• Anyone with dedication. Background doesn’t limit success; effort, continual learning, and adaptability to evolving tech determine outcomes.

Cloud Engineering and DevOps: Scope, differences, and learning paths (Yuxiao & John)

What cloud engineering entails (Yuxiao)

• Don’t fixate on vendor tools; master the underlying disciplines: infrastructure, networking, security, automation, and how applications run in the cloud.
• Typical responsibilities: Hosting architecture, networking, DNS, load balancing, compute, storage, databases, connectivity, and securing reachability for the right users.

Cloud Engineer vs DevOps Engineer (Yuxiao)

• Cloud Engineer: Provisions and configures cloud infrastructure (networking, compute, storage, managed services), security baselines, and connectivity.
• DevOps Engineer: Sits between development and operations, enabling deployment, CI/CD, and release reliability on the cloud resources the cloud team provides.
• Note: In many organizations (especially smaller/less structured ones), the roles are blended; in mature orgs, they are distinct teams.

Yuxiao’s learning journey and advice

• Transitioned from teaching; self-studied enough to secure an internship; hired based on demonstrable skills and teachability.
• Learned Azure extensively in a Microsoft-partner environment under live customer pressure: networking (App Gateway, Front Door, firewalls), IaaS (VMs), PaaS (App Services, Static Web Apps), observability (Application Insights), etc.
• Faced intense KPIs and high-stakes customer support; nearly quit but anchored on his “why.” Experience plus self-study enabled a later move into DevOps (Linux, containers, Docker, Kubernetes, Terraform).
• Start with one major cloud (AWS, Azure, or GCP). Concepts are transferable; naming differs:
  • Azure Virtual Machines ≈ AWS EC2 (compute)
  • Azure Virtual Network ≈ AWS VPC (networking)
  • Master one provider deeply; then map concepts to others.

John’s learning journey and practical insights

• Early PC exposure led to modding games and understanding file systems/OS internals; later formalized with AWS Cloud Practitioner and pivoted into DevOps.
• Pitfall: “Shiny object syndrome.” Don’t skim many tools; master the basics first (OS, networking, Git, Bash/scripting, Linux), then progress to containers (Docker), orchestration (Kubernetes), and IaC (Terraform, etc.).
• What to expect in DevOps:
  • Upsides: You’ll see the back end of how systems truly work (system design, distributed behavior, reliability constraints).
  • Downsides: On-call/late hours and the weight of operational decisions; seemingly small choices can have major cost/reliability impacts.
    • Example: Using Kubernetes for a simple 3-tier app inflated costs vs. a serverless option (e.g., Cloud Run) that would have met needs at a fraction of the price. Architectural choices carry financial and operational consequences.
• Choosing between Cloud and DevOps: Often depends on the environment/team’s structure. If you enjoy debugging applications and deployment pipelines, DevOps may fit; if you prefer provisioning platforms and architectures, Cloud Engineering may fit. Many roles blend both.

Career impact and rewards (All speakers)

• Halima: Cybersecurity is life-changing with accelerated growth for those who deliver. Broad, cross-company networking and knowledge sharing are central. Teaching/mentoring amplifies impact.
• Yuxiao: The field met financial goals and offers job security and lower competition. Pay correlates with experience and skill; age is not a limiter. You develop a deeper understanding of systems and meet many smart peers.
• Kenneth: The skills travel globally; work with international clients from anywhere. Builds confidence and networks with senior stakeholders. Financially rewarding if you remain consistent and ethical.

Bootcamp structure, mentorship, and logistics (Host)

• Live classes with accessible tutors; engage respectfully and actively.
• Post-bootcamp alumni community with mentorship sessions, opportunities, and ongoing support; many alumni retain ties with tutors who share job leads.
• Applications close tomorrow; selection of awardees next Thursday. A track-switch window will be announced in the community. Stay active and follow community updates (all key dates are posted there).

Q&A highlights

• Mentorship access if not selected: The bootcamp embeds mentorship during the program; post-bootcamp, alumni receive ongoing mentorship via the community. Deep one-to-one mentorship typically stems from relationships built during the program; maintain professional, proactive engagement with tutors.
• Programming in cybersecurity: Not required at the very start. As you advance, being able to read code helps (e.g., understanding web app issues). AI-assisted workflows can help interpret code. Focus first on security and system fundamentals.
• “How many years to be an expert?”: No fixed timeline; titles and expectations vary by organization. Broadly, recognized expertise mixes substantial hands-on practice, technical depth, people/process competencies (calm under pressure, team leadership), and adaptability.
• Tools the cybersecurity track touches: A structured curriculum introduces relevant tools over time (e.g., Wireshark, Cisco Packet Tracer, and others), aligned to each domain and module.
• Daily habits for beginners:
  • Follow security news daily; discuss incidents with peers/tutors.
  • Learn one concept at a time; avoid parallel overload.
  • Collaborate, ask questions, and work on small, tangible projects regularly.
  • Use appropriate tools (proper laptop/desktop) for realistic practice.
• Cloud/DevOps and coding: Details of each track’s curriculum will be provided in the community. From the discussion, DevOps foundations include Linux, Git, Bash/scripting, infrastructure-as-code, containers/orchestration; cloud roles require fluency with cloud services and automation.

Actionable takeaways for beginners

• Start with fundamentals: Linux, networking, platform basics (applies across security, cloud, DevOps, and even hacking).
• Pick a lane to begin: Don’t try to learn everything at once. Build depth in one area before branching out.
• Learn the system before securing/attacking it: Architecture-first thinking is mandatory.
• Practice documentation: Write clear, business-aware reports; refine your presentation skills.
• Collaborate deliberately: Seek peers, form study groups, and learn from others’ approaches.
• Be tool-realistic: Get a capable laptop/desktop; simulate enterprise environments.
• Build habits: Daily news, weekly projects, regular reviews, and reflective notes.
• Consider certifications: They complement hands-on skill and signal readiness to employers.
• Remember your “why”: It sustains you through steep learning curves and high-pressure moments.
• Engage the community: Join and stay active in program channels; watch for track-switch windows and key dates; build relationships with tutors and peers.

Closing

The session underscored that success across Cybersecurity, Ethical Hacking, Cloud, and DevOps is less about initial degrees and more about consistency, curiosity, structured learning, collaboration, and communication. With the right foundation, focus, and community support, beginners can progress to meaningful, well-compensated roles that have global relevance and impact.