HOROIHEOMA C.
Nigeria · Cybersecurity Analyst · Telecoms sector (Geek Force)
NYSC
11 followers
About
Cybersecurity Analyst with over 12 years of experience in telecoms technical support, access control, and security incident detection and resolution. Skilled in SIEM monitoring, alert triage, log analysis, Active Directory, firewall configuration, and endpoint security using Wazuh, FortiClient, and Wireshark. Possesses practical SOC, vulnerability assessment, and network monitoring experience, with a strong analytical mindset and commitment to continued cybersecurity development.
Skills
- SIEM monitoring & alert triage
- SOC workflows & incident escalation
- Incident Response
- Log analysis & correlation
- Threat intelligence & OSINT techniques
- IDS/IPS monitoring & rule tuning
- FortiClient/FortiAgent configuration
- Firewall policy configuration
- Host-based monitoring (Wazuh)
- Vulnerability assessments
43 skills in total
Licenses & Certifications
-
Certified in Cybersecurity
ISC²
Issued Mar 2026 · Expires Feb 2029
Experience
-
Telecoms sector (Geek Force)
-
Cybersecurity Analyst / Technical Customer Support (Geek Force)
Jan 2012 — Present
-
Cybersecurity Analyst / Technical Support Specialist
Jan 2012 — Present
-
Education
-
NYSC
National Youth Service Corps (NYSC)
Jan 2008
-
Abia State University, Uturu
B.Sc., Biotechnology
Jan 2000
4 education entries in total
Recent posts
My journey through cybersecurity has been a tough yet interesting one. I have always dreamed of applying my acquired skills professionally, no matter how small the opportunity. To God be the Glory, that dream is becoming a reality!
I’m excited to announce that I have been selected for a Cybersecurity Internship at Networkwalks, running from 25 October to 22 November 2026.
This is an opportunity to move beyond learning and lab practice into gaining practical industry experience in areas such as network security, vulnerability assessment, penetration testing, SOC operations, incident response, and digital forensics.
I’m grateful for this opportunity to learn, grow, challenge myself, and take another meaningful step toward my cybersecurity career goals.
One step at a time, one skill at a time, one opportunity at a time. The journey continues, and this is just the beginning!
A big thank you to @NETWORKWALKS ,@Waqas Karim (CCIE) and Prosper Njoku for this opportunity.
#Cybersecurity #CybersecurityInternship #InfoSec #SOCAnalyst #ContinuousLearning
Following up on my capstone Project: The Executive Debrief .
After the full report, the next challenge was a different one: explaining the same project to a board that is short on time,non-technical, and focused on risks and costs. I've attached the executive debrief slides ( https://acrobat.adobe.com/id/urn:aaid:sc:EU:6ea20f2f-68d7-419c-9843-cd39a2e04ea7 ) from my AI in Cybersecurity capstone class project at Brixgate academy.
It takes one flagged login sequence in a fictional fintech and turns it into a story a board can act on immediately: what happened, what it could cost, and what to fix first.
Writing the technical report was one skill. Telling the story in plain words was another. The slides had to explain what matters, why it matters, and what to do next, with no tool names and no jargon.
The lesson from the project still holds. AI can speed up the work, but judgement is still the humans job. Thank you again to Brixgate for a programme that pushed me to think, not just prompt. Feedback is welcome.
#Cybersecurity #AIinCybersecurity #Threatintelligence #IncidentResponse #SOC #GRC #BrixgateAcademy #ContinuousLearning file:///C:/Users/Administrator/Downloads/NimbusPay_Executive_Debrief.pdf
Just defended my capstone project for the AI in Cybersecurity programme, and I'm still excited about how it went.
The project simulated an end-to-end security assessment for a fictional fintech, working across four areas: researching a real threat actor and its history of targeting financial platforms, running passive reconnaissance with shodan.io and ollama to uncover exposed systems, triaging a live looking credential-stuffing incident and building an AI-augmented incident response playbook, and closing it out with a compliance gap analysis against recognized security frameworks(ISO 27001).
Throughout, I worked hands-on with Ollama (running local models) and Claude Code, using them the way I'd expect to in a real SOC — as a research and drafting accelerant, never as the final word.
That's exactly why AI matters so much across this field right now:
In threat intelligence, it can turn hours of research into a structured briefing in minutes — but every claim still needs a human to check the source.
In a SOC, it can triage and rank alerts faster than any analyst — but it can't yet tell a real account takeover apart from a legitimate customer having a bad login day(false positives).
In incident response, it can draft the playbook, the timeline, the customer notice — but every action that actually locks an account or freezes a transfer still needs a named human to approve it.
In compliance, it compared our policies against two ISO 27001 controls — Authentication Information/Access control and Logging/monitoring — and flagged real gaps in minutes: no multi-factor authentication or password rotation requirement, no least-privilege access model, no formal incident response plan, and no clearly defined incident-response roles.
Fast and useful, but the legal and regulatory judgment call still belongs to people.
AI didn't replace the analyst anywhere in this project. It just moved the human's attention from typing to thinking — which, if used right, is exactly where it should go.
A few things that stuck with me:
A weak prompt gets you a guess. A structured one that spells out the role, the context, the objective, and clear constraints — gets you something detailed and comprehensive.
"The AI said so" is never the end of an investigation always bearing in mind ai hallucinations and overreacting) .
The best security work still starts and ends with a human asking, "wait, is that actually true?"
Huge thanks to Brixgate for building a programme that didn't just teach AI tools, but taught how to think critically alongside them. That's the skill that is going to matter most as this field keeps moving.
Looking forward to putting this into practice.
#Cybersecurity #AI #ThreatIntelligence #IncidentResponse #SOC #GRC #BrixgateAcademy #Ollama #ClaudeCode
OPERATION RESOLVE & TRACE: SOC ANALYST CTF CHALLENGE:
Challenge Scenario
Your Security Operations Center (SOC) SIEM has raised alerts regarding anomalous network traffic and DNS queries generated by multiple hosts. As a Tier-1 SOC Analyst, you are assigned a specific target domain, public IP, and an internal private subnet segment to investigate. Your goal is to conduct DNS reconnaissance, verify infrastructure records, trace reverse DNS mappings, evaluate IP reputation, and perform authorized port validation.
https://freedcamp.com/view/3762809/tasks/panel/task/72585518
Over the past few weeks i enrolled for AI in cybersecurity with Brixgate and have been privileged to run hands-on experiments on AI for SOC in a controlled environment .It's getting interesting already!
Using AI models like(Ollama, MiniMax, and Claude) to handle real SOC workflows (alert triage, detection logic, even parts of incident response).
Plugging them into the day to day grind of a Security Operations Center.
The real enemy as a SOC analyst isn't sophistication but volume. Hundreds of alerts a day, most of them noise, a few of them real. Analysts burn out triaging the same false positives over and over, and the one alert that matters can get lost in the pile. So where do these tools actually fit in?
Ollama — running models locally means I can process sensitive logs and alert data without it ever leaving my environment.
MiniMax — surprisingly capable for fast, lightweight reasoning tasks: It's not going to write your incident report, but it's quick and cheap enough to run on everything.
Claude — this is where the deeper reasoning happened. Correlating alerts across different log sources, drafting a clear summary of what actually happened, suggesting next investigative steps. The kind of output a junior analyst would take twenty minutes to write, generated in seconds, and honestly readable enough to hand straight to a lead.
Contrary to many beliefs,Ai is not here to "replace the analyst." It s just compressing the boring 80% of the job (reading, correlating, summarizing ) so the human gets straight to the 20% that actually needs judgment.
Detection, triage, and even firstdraft response actions that used to take a full shift now happen in a fraction of the time.That said,these models still need, human review, and a lot of prompt tuning before you'd trust them on a real production SOC floor.
I also leaned about ai hallucination that posses a great risk ( AI hallucination is when a model generates output that sounds confident, but is factually wrong or entirely made up. The model isn't lying on purpose , it doesn't know it's wrong. It's just predicting the most statistically likely next words based on patterns it learned, and sometimes that pattern lands on something false rather than true)
My takeaway:
>The SOC of the near future probably isn't "AI replacing analysts." It's AI doing the first pass on everything, so analysts spend their energy where it actually matters .
>Instead of using weak prompts, it is best to use strong ,specific, structured prompts with roles, contexts and objectives to get desired and elaborate results.
Still early days for me on this though, but I'm convinced this is where security operations is heading. Curious if others are experimenting with this too .
#CyberSecurity #SOC #AI #ThreatDetection #Ollama #Claude #InfoSec #Brixgate