Ikechukwu O.
Lagos State, Nigeria · Security Operations Center (SOC) Analyst · Self-Employed / Project-Based Consulting
Imo State University, Owerri, Nigeria
37 followers
About
Results-oriented SOC Analyst with extensive experience in vulnerability management, secure infrastructure design, and incident response. Skilled in monitoring and triaging alerts using SIEM, EDR, and IPS tools, with a proven trackable record of reducing false positives and improving response times in hybrid environments.
Specialties
- Malware Analysis
- Network Defense
- Security Monitoring
- SIEM Engineering
- Threat Detection
Skills
- SOC Analysis
- SIEM
- EDR
- IPS
- Vulnerability Management
- Incident Response
- Next-Generation Firewalls (NGFW)
- pfSense
- Fortinet
- Microsoft Intune
76 skills in total
Licenses & Certifications
-
Certified Cybersecurity Educator Professional (CCEP)
Red Team Leaders
Issued Nov 2025
-
CompTIA Security+
CompTIA
Issued Apr 2026 · Expires Apr 2029
-
Fortinet Certified Associate in Cybersecurity
Fortinet
Issued Feb 2026 · Expires Feb 2028
4 certifications in total
Experience
-
Cloud and Security Projects
Self-Employed / Project-Based Consulting
Sep 2025 — Present
Remote
-
Security Operations Analyst
Torf Technologies
Jul 2023 — Sep 2025
Lagos State, Nigeria
-
IT Support Specialist
Excel Group
Aug 2021 — May 2023
Nigeria
Education
-
Imo State University, Owerri, Nigeria
Oct 2014 — Jul 2018
Recent posts
If there are no logs in Sentinel, you have zero visibility and zero detection.
While building out my Microsoft Sentinel lab, I hit a critical wall: Windows Security Events simply stopped flowing. For any SOC analyst, this is a nightmare scenario where authentication activity, privilege escalations, and IOCs vanish into a black hole.
Here is how I diagnosed the failure and restored the pipeline:
🔎 The Resolution Path
1️⃣ Validate the Source: I started by opening Windows Event Viewer on the VM. Local generation of events like 4624 (Logon) and 4625 (Failed Logon) was functioning perfectly, confirming the issue wasn't the OS.
2️⃣ Identify the Gap: I traced the telemetry upstream and found the Windows Security Events via Azure Monitor Agent (AMA) connector had lost its link to the Log Analytics workspace. The data existed but had no path to the cloud.
3️⃣ Re-engineer the Flow: I reconfigured the AMA connector, applied the correct Data Collection Rule (DCR), and successfully bridged the ingestion gap.
4️⃣ Verification: Within minutes, KQL queries for SecurityEvent IDs 4624, 4625, 4672, and 4798 confirmed that privileged logons and group enumerations were officially back on the radar.
✅ Key Takeaways for Defenders:
▶️ Systematic Diagnosis: Troubleshoot in layers (OS → Agent/Connector → Workspace) to isolate the failure point quickly.
▶️ Trust but Verify: Event Viewer is your source of truth. Always confirm logs exist locally before chasing phantom configurations in the portal.
▶️ Stealth Failures: A misconfigured AMA connector is a silent killer for SOC visibility. Regular health checks on ingestion heartbeats are non-negotiable.
This lab was a perfect exercise in troubleshooting high-stakes ingestion issues and ensuring SOC readiness-skills that are mandatory for securing enterprise environments.
#SOCAnalyst #MicrosoftSentinel #CyberSecurity #AzureSecurity #IncidentResponse #SC200
Quick cybersecurity reality check: Buying a SIEM does not mean you are secure.
Out of the box, most security monitoring tools are completely blind to unique business and application logic. If you aren't actively engineering your detections, you're blind to real threats.
I recently ran a project simulating a fintech ecosystem to put this to the test. By building custom log ingestion pipelines and authoring targeted XML signatures, I configured the environment to catch high-severity exploits like RCE, SQLi, and API parameter tampering that standard signatures missed entirely.
The biggest takeaway? The true value of a modern SOC isn't the platform you deploy; it's the custom engineering and systematic tuning you do under the hood to eliminate false positives and catch true attacks.
the JASPER_BANK is an intentional vulnerable web application I designed with AI for simulation and never a real infrastuture. 😊
Back to building. 💻🔥
#DetectionEngineering #Cybersecurity #SIEM #Wazuh #BlueTeam #SOC #Fintech
I am officially open to new opportunities in Security Operations. I have built strong, hands on experience in hybrid SOC environments, improving infrastructure security, tuning SIEM pipelines, and applying practical security policies across cloud and on prem systems. I enjoy threat hunting, alert triage, and incident response, and my lab portfolio shows real and continuous learning, job ready capability. I am ready to bring my skills, curiosity, and drive to a SOC Analyst or Security Associate role. Any recommendations will be highly vlaued.
Thank you.
Cybersecurity is never about a single 'fix,' yet that is often how we teach it. We tell people to 'use a strong password' and act like the job is done. What is on my mind is how we can better teach the concept of 'Defense in Depth' to the average user. Security is a mindset of layers; technical, behavioral, and analytical, and that is a mindset we should be cultivating early.