Information Security · GRC · Security Assessment · Corporate Training
I work as a cybersecurity manager, combining hands-on security assessment with information-security governance, risk and compliance. My work spans web and API security, network security, practical tooling, research and teaching. This portfolio brings together tools I build, coauthored research and learning resources.
My personal site is abdullahzarshaid.com. ABZSECURE is the consultancy and training brand I run. This GitHub account holds my own tools, research and teaching material.
Try PostureKit · Try EvidenceGate · Read the handbook · Pick a GRC tracker
Latest (17 October 2026): PostureKit 0.6 and EvidenceGate 1.0.0 are tagged releases with continuous tests on Linux, Windows and macOS, project pages and citation files; the handbook's October 2026 edition and the GRC trackers 1.0.1 are downloadable releases. Next: a Web and API penetration testing manual, lab targets only, written from the basics up.
Use a tool: PostureKit demo · EvidenceGate demo
Learn the workflow: From Scope to Security Evidence
Run security work in spreadsheets: six GRC trackers, pick one online
- PostureKit: Windows, directory and wireless configuration assessment: evidence collection, rule-based analysis and scanner imports. Project page.
- EvidenceGate: local integrity, HTTP capture-structure, CVSS and scope checks for security assessments. Project page.
- GRC Excel Starter Templates: six original MIT-licensed blank trackers for risk, evidence, remediation, vendors, policies and assessment scope. Not complete framework checklists or certification tools. Browse online.
- Network Security Assessment Handbook: methodology, worked scenarios and protocol reference. Read online.
- Ethical Hacking Labs: 19 topic guides for isolated practice, with credited student examples.
CWE proposal, explicit session termination
I submitted Improper Enforcement of Explicit Session Termination to the CWE Program. The proposal is publicly tracked in the CWE Content Development Repository, issue #224, submission ES2609-7b54439f.
Status checked 25 September 2026: receipt acknowledged (Phase02-Ack-Receipt); evaluation pending. This is a proposal, not an assigned or accepted CWE entry. The linked issue is the source for subsequent status changes.
Session-lifecycle research
Lifecycle Conditions in CWE-613 Disclosures: A Reproducible, Evidence-Linked Characterisation (earlier working title Logout Is Not Expiration), with Shahbaz Akhtar Siddiqui. Manuscript under peer review; the data and code repository will be opened when the review concludes. Record on ORCID.
Build & automate
Python · PowerShell · Bash · Git
Platforms & environments
Kali Linux · Linux · Docker · Microsoft Azure
Security assessment & analysis
Burp Suite · Nmap · Wireshark · Metasploit
Also in the assessment workflow: Greenbone / OpenVAS and Active Directory.
- Evidence before conclusions. Keep observations, interpretations and confirmed impact distinct.
- Clear scope. Assess only authorized systems; keep private engagement material out of public examples.
- Useful artifacts. Prefer inspectable Python and PowerShell, documented limits and reproducible examples.
- Assess & investigate: Web and API security; network and wireless assessment; Windows, Active Directory and cloud configuration.
- Govern & improve: Information-security governance; risk assessment; control mapping; evidence quality and remediation tracking.
- Teach & research: Corporate training; practical labs; assessment methodology; reproducible security research.
Teaching materials retain contributor credit; research identifies its coauthors and publication status in the project repository. My earlier master's work on SDN-enabled IoT security is being revisited; it is not presented here as a new released tool or a published result.
OWASP · NIST Cybersecurity Framework · MITRE ATT&CK · PortSwigger Web Security Academy
These are independent third-party resources, not my projects or endorsements of my work.
LinkedIn · Website · ABZSECURE · ORCID · Email
For a tool issue, please use its repository's issue tracker with a synthetic, sanitized example, never live credentials or client evidence.
