Hisham Mir is a cybersecurity professional with 10+ years of hands-on experience and Co-Founder & CTO of SecurityWall. He leads real-world penetration testing and vulnerability research, and is an experienced bug bounty hunter.
LLM Security
Jailbreaking Isn’t a Prompting Problem For a long time, jailbreaks were treated as a curiosity. Someone found a clever prompt, it circulated online, a filter was adjusted, and the incident was written off as an edge case. If you’ve spent years in application security, this likely felt familiar
NESA
Organizations operating in the UAE increasingly find themselves navigating multiple cybersecurity and compliance frameworks at the same time. What often starts as a governance initiative such as ISO 27001 certification quickly becomes more complex once national regulatory requirements like NESA and oversight by SIA enter the picture. This complexity leads
NESA
Most organizations do not fail NESA assessments because of missing security tools. They fail because governance, evidence, and accountability are not structured in a way regulators expect. A NESA audit is not a certification exercise or a third-party review. It is a regulatory assessment focused on how effectively an organization
NESA
As NESA assessments and regulatory reviews approach, organizations often realize that compliance gaps are rarely technical alone. More often, challenges stem from unclear governance, incomplete evidence, or misaligned risk management practices. This NESA compliance checklist is designed as a readiness guide for CISOs, compliance managers, and risk leaders who are
UAE Compliance
For organizations that already know what NESA is, the next challenge is understanding what NESA compliance actually requires. This is where many compliance managers, CISOs, and risk leaders get stuck. These requirements apply broadly across sectors in the UAE and are governed by the national cybersecurity framework explained in our
UAE Compliance
NESA, NESA UAE, and NESA compliance have increased steadily as cybersecurity regulation in the UAE matures. Yet many organizations still struggle to understand what NESA actually is and whether it applies to them whereas same goes for NESA Audit and assessment process. To understand the specific security domains, controls, and
JWT Security
Our previous guides cover how to securely design, configure, and analyze JSON Web Tokens including JWT Security Best Practices, the hands-on JWT Analyzer Security Checker Guide, and JWT Analyzer vs Other Token Debuggers this post shifts the focus entirely to JWT pentesting. Instead of defensive configuration or tool usage, it
Security Trends
CES 2026, held from January 6–9 in Las Vegas, clearly shows that cybersecurity is no longer a secondary layer around artificial intelligence. This year, AI security itself is part of the core innovation narrative. Across hardware vendors, platform providers, and startups, the message is consistent: AI systems that are
SLASH
Modern organizations ship software faster than ever but most penetration testing models haven’t kept up. Annual penetration tests, static reports, and point-in-time assessments were designed for a slower era. That gap is exactly why PTaaS (Penetration Testing as a Service) exists. In this guide, we’ll explain what PTaaS
JWT Security
In earlier articles, we examined how JWT implementations fail in practice and how to use the JWT Analyzer & security checker. This post builds on that foundation, but shifts the focus away from JWT mechanics and tooling walkthroughs. Instead, it addresses a recurring decision point we see across engineering and
JWT Security
JSON Web Tokens are a core part of modern authentication and API security, which is why searches for a reliable JWT security checker or JWT analyzer continue to grow. While JWTs are easy to generate and integrate, they are also easy to misuse in ways that are not immediately visible
JWT Security
JSON Web Tokens (JWTs) sit at the center of modern authentication and API security. They are simple to issue, easy to transport, and dangerously easy to misuse. Most JWT-related incidents are not caused by broken cryptography. They are caused by incorrect assumptions about what JWTs guarantee, incomplete validation, and a