Ahmad T.

Ahmad T.

Lagos · Threat Intelligence and Research Analyst

University of Ilorin, Nigeria

11 followers

About

My approach to Cybersecurity is defined by scientific precision and business-aligned risk management. With a background in Chemistry, I treat network telemetry like laboratory data, applying rigorous analytical methods to identify anomalies and disrupt the attack lifecycle before it affects the bottom line.

Core Technical Stack & Competencies:

Detection Engineering: Engineering high-fidelity rules and KQL queries to transform raw logs into actionable intelligence.

Security Automation: Building end-to-end incident response workflows using Wazuh and Shuffle SOAR to eliminate manual bottlenecks.

Enterprise Defense: Managing security posture across Microsoft 365 E5 (Certified SC-200 / SC-900).

Strategic Compliance: Aligning technical controls with ISO 27001 standards to ensure both security integrity and organizational compliance.

Specialties

  • AWS Security
  • Cyber Threat Intelligence
  • Penetration Testing
  • Security Engineering
  • SOC Analyst

Skills

  • Analytical Skills
  • Analyze Information
  • C++
  • Chemistry Education
  • Communication
  • Customer Service
  • Cyber Threat Intelligence (CTI)
  • Cybersecurity
  • Database Tools
  • Decision-Making

45 skills in total

Experience

  • Threat Intelligence and Research Analyst

    Smartcomply

    Nov 2025 — Jun 2026

    Lagos State, Nigeria

  • Security Analyst

    3MTT Nigeria

    May 2025 — Jul 2025

    Nigeria

  • Junior Penetration Tester

    wHTa Networks

    Nov 2024 — Feb 2025

    Kenya

4 experiences in total

Education

  • University of Ilorin, Nigeria

    Bachelor of Science, Chemistry

    May 2015 — Oct 2019

Repositories

Recent posts

🚨 PHP2Shell: A Reminder That Visibility Matters More Than Ever

Imagine a security flaw hiding inside software that's quietly run the web for decades. Not a new app. Not some obscure plugin, but one of the core technologies behind a huge share of the internet.

That's the story behind PHP2Shell.

PHP is a server-side language used to build and run websites and web applications. It powers platforms like WordPress, Drupal, and Joomla, plus countless business sites and online services. Estimates put its footprint at roughly 70% of websites, but that doesn't mean 70% of the internet is vulnerable. It shows how much surface area one flaw in PHP itself can touch.

The flaw beneath the applications:

On October 21, 2026, the PHP project disclosed two critical bugs in its core runtime: CVE-2026-109618 and CVE-2026-109619. Both scored 9.2 (Critical), and neither requires a login to exploit.

Both trace back to how PHP handles memory. One is triggered by a crafted upload or form submission that leaves PHP working with data that wasn't fully set up. The other lets leftover data from one request get read by the next request on the same server, even from a different user.

Put together, this could let an attacker run their own code on the server with no credentials at all, opening the door to stolen data, defaced sites, or a foothold into connected systems.

Why this is really about visibility, not just patching.

Finding the vulnerability was only ever half the problem. The harder half is knowing where that technology actually lives: which servers, which forgotten apps, which old VM nobody's touched since 2019.

That's why quarterly scans and slow patch cycles aren't enough anymore. What matters is whether an organization knows, continuously, where it's exposed.

🔹CTI tells you a flaw like this exists, who's using it, and how fast.

🔹EASM tells you which of your internet-facing assets are actually running the vulnerable code, including the ones no one remembers.

🔹CAASM ties it together internally, across cloud and on-prem, so "we patched it" means patched everywhere, not just where someone happened to look.

A forgotten domain. An old VM. Any one of these can quietly undo an otherwise mature security program.

The next major security challenge probably isn't finding the vulnerability. It's finding every place it lives before someone else, human or AI, does it first. That's not a patching problem. It's a visibility problem.

View post

I’ve been developing PhilSIEM, my own hands-on cybersecurity project, combining honeypot monitoring, threat intelligence and security event analysis.

The goal is to build a practical environment for detecting suspicious activity, investigating alerts and developing real-world SOC analyst skills.

The project is still evolving, with some exciting developments planned around automated detection and AI-assisted analysis.

🌐 https://philsiem.com

I’d love to hear feedback from fellow cybersecurity professionals, SOC analysts and enthusiasts.

Feel free to take a look and let me know what you think!

#CyberSecurity #PhilSIEM #SOCAnalyst #ThreatIntelligence #BlueTeam #HomeLab #InfoS

View post

"Why would anyone bother targeting us?" might be one of the most expensive questions an organization can ask when it's being used to justify doing nothing. I've heard variations of that argument throughout my career, usually somewhere between a CTI assessment identifying a credible threat and a discussion about why remediation needs to wait until the next budget cycle. And I understand the temptation, because preventive security spending is immediate, visible, and relatively easy to question, while the cost of an incident that hasn't happened yet is hypothetical and conveniently absent from the balance sheet.

Unfortunately adversaries don't necessarily care whether we consider ourselves important enough to target. Sometimes we're valuable because of the information we hold, the services we provide, the organizations we're connected to, or simply because we're an accessible stepping stone toward something else. That's where dismissing CTI becomes a business decision, whether leadership recognizes it or not.

When intelligence identifies a credible exposure and the organization chooses to defer remediation, it isn't avoiding a cost. It's accepting a risk whose eventual price may include incident response, forensic investigations, legal expenses, operational downtime, lost revenue, customer attrition, regulatory scrutiny, and months of recovery work. Compare that with the often considerably smaller cost of preventive maintenance, targeted remediation, compensating controls, or architectural improvements before an adversary gets involved.

What bothers me isn't that organizations sometimes accept risk, because there are perfectly legitimate business reasons to do so. It's when they accept that risk without understanding the potential consequences, or dismiss the intelligence because the threat doesn't fit their perception of who would find them interesting.

CTI should help leadership distinguish between theoretical exposure and credible business risk, quantify the consequences where possible, and understand what they're buying with remediation versus what they're gambling by deferring it. And we should be measuring that decision over time, because a vulnerability left unresolved for six months isn't necessarily the same risk it was when the original assessment was written.

I wonder how many organizations would make different decisions if every deferred remediation carried an estimate of the operational and financial consequences of being wrong, alongside the actual cost of fixing it. If preventing a breach costs $50,000 and recovering from one could cost $5 million, are we really saving money by postponing remediation, or just betting the business that nobody notices before we get around to it? CTI may be classified as 'overhead' but if that same 'overhead' saves money in the long run shouldn't we begin to consider it more like flipping a cost center into a revenue generator?

View post

The Architectural Manifesto: Part 2 — Why "Black October" Proves Your Threat Model is Dead.

The global cybersecurity ecosystem is scrambling over the new PHP "php2shell" zero-days (CVE-2026-109618 & CVE-2026-109619).

CISA is yelling to patch, tech stacks are forcing emergency offline modes, and AI-enabled hacking tools are already attempting unauthenticated Remote Code Execution at machine speed.

But here is the architectural reality everyone is missing:

The infrastructure didn't just fail because of a programming language bug. It failed because enterprise architecture still treats boundary validation as an afterthought.

If your security architecture requires you to maintain absolute, real-time awareness of every dependency just to prevent a total takeover, you haven't built a defense strategy. You’ve built a house of cards.

Traditional AppSec relies on a broken loop: Vulnerability Discovered ➔ Emergency Patch Developed ➔ Human Team Triage ➔ Network Exposed For Days.

At ETBV, we engineered a clean break from this cycle.

Instead of racing AI-driven exploit tools to apply signatures, our Layer Zero gate enforces deterministic pre-execution isolation. It does not matter if a zero-click exploit bypasses an application-layer firewall. If the payload attempts unauthorized shell initiation or command injection, the execution plane natively isolates it before a single instruction reaches the core OS.

We don't try to guess the bug. We invalidate the execution path.

The result? Threat vectors are neutralized natively at the boundary, streaming clean, STIX 2.1-compliant telemetry back to the fleet without adding operational latency.

Stop patching symptoms while leaving the architecture vulnerable.

Read the full engineering breakdown of our Layer Zero matrix in our pinned master framework.

How is your engineering team neutralizing php2shell without dragging web infrastructure offline? Let's debate in the comments.

View post

The Architectural Manifesto: Part 2 — Why "Black October" Proves Your Threat Model is Dead.

The global cybersecurity ecosystem is scrambling over the new PHP "php2shell" zero-days (CVE-2026-109618 & CVE-2026-109619).

CISA is yelling to patch, tech stacks are forcing emergency offline modes, and AI-enabled hacking tools are already attempting unauthenticated Remote Code Execution at machine speed.

But here is the architectural reality everyone is missing:

The infrastructure didn't just fail because of a programming language bug. It failed because enterprise architecture still treats boundary validation as an afterthought.

If your security architecture requires you to maintain absolute, real-time awareness of every dependency just to prevent a total takeover, you haven't built a defense strategy. You’ve built a house of cards.

Traditional AppSec relies on a broken loop: Vulnerability Discovered ➔ Emergency Patch Developed ➔ Human Team Triage ➔ Network Exposed For Days.

At ETBV, we engineered a clean break from this cycle.

Instead of racing AI-driven exploit tools to apply signatures, our Layer Zero gate enforces deterministic pre-execution isolation. It does not matter if a zero-click exploit bypasses an application-layer firewall. If the payload attempts unauthorized shell initiation or command injection, the execution plane natively isolates it before a single instruction reaches the core OS.

We don't try to guess the bug. We invalidate the execution path.

The result? Threat vectors are neutralized natively at the boundary, streaming clean, STIX 2.1-compliant telemetry back to the fleet without adding operational latency.

Stop patching symptoms while leaving the architecture vulnerable.

Read the full engineering breakdown of our Layer Zero matrix in our pinned master framework.

How is your engineering team neutralizing php2shell without dragging web infrastructure offline? Let's debate in the comments.

View post

View Ahmad T.'s profile on Cyberr