Hi,
I’m Rokibul
an Offensive Security Engineer & Cybersecurity Specialist
I came to offensive work from the defensive side, which is a slower route and a better one. It started at TechForing with vulnerability assessments, penetration tests and forensic investigations. At DITECH I ran vulnerability management, SIEM-driven investigations and system hardening, including a set of custom Splunk dashboards that lifted detection accuracy by around 30% — mostly by cutting the noise analysts had learned to click through rather than by adding new rules. I now work independently, delivering full-scope web, API and cloud penetration tests for enterprise clients. Recurring test modules are automated in Python with AI assistance, which takes roughly 25% off reporting time; that time goes back into testing, not into shipping the report sooner. Findings come out CVSS-rated and mapped to MITRE ATT&CK, with the caveat that a base score deliberately encodes nothing about your business, so severity and urgency stay separate columns.
The work runs end to end: reconnaissance, reverse engineering, exploitation, and the post-exploitation validation most reports skip — proving what an initial foothold actually reaches, rather than stopping at the foothold. The toolchain is unremarkable on purpose: Ghidra, Burp Suite, OWASP ZAP, Nmap, Metasploit, and Python and Bash where nothing off the shelf fits, with assessments aligned to OWASP and the CIS benchmarks. Having sat on the blue side first changes the output. Every finding gets a note on what it would have looked like in the logs, and whether your existing tooling would have caught it — because a vulnerability nobody can detect is a different problem from one nobody has patched. Open to offensive security roles internationally and to remote freelance engagements.
My career journey so far
Three roles, one direction: monitoring other people's alerts, then owning the detections, then attacking the systems that generate them. The blue-team years are why the findings come with detection notes.
Download CV-
Oct 2021 - Sep 2022 | Dhaka, Bangladesh · On-site
Jr. Cyber Security Engineer
TechForing · Full-time
Vulnerability assessments, penetration tests and forensic investigations on enterprise systems, alongside senior engineers who were unsparing about the difference between a scanner hit and a finding. Nessus, Wireshark and Burp Suite daily. The work that mattered least on paper and most in practice was the internal knowledge base — writing down the recurring scenarios so the next person did not rediscover them from scratch.
-
Oct 2022 - Mar 2024 | Dhaka, Bangladesh · On-site
Cyber Security Specialist
DITECH · Full-time
Owned vulnerability management, SIEM investigations and incident response. The custom Splunk queries and dashboards raised detection accuracy by about 30%, and most of that came from deleting rules whose false positives had trained everyone to ignore them. Also learned where hardening actually stalls: patch cycles are an engineering-scheduling problem long before they are a security one, and CIS and ISO 27001 alignment is worth little if the exception register is where uncomfortable findings go to be forgotten.
- S
Apr 2024 - Present | Dhaka, Bangladesh · Remote
Freelance Offensive Security Engineer
Self-Employed
Full-scope web, API and cloud penetration tests for enterprise clients. Automation handles coverage and the repeatable checks; the findings worth paying for still come from reading the application and working out what its logic assumes. Ghidra, Burp Suite and Metasploit where they fit, Python where they do not. Automating the recurring modules takes roughly 25% off reporting time, which is time returned to testing. Reports are CVSS-rated and ATT&CK-mapped, with business urgency kept as its own field — a base score is designed not to know what your system is worth.
Check my Github Repositories
Most of what I build starts as something I needed twice in one week. The repositories cover penetration testing helpers, malware analysis scaffolding, incident response tooling and network security work — written for real engagements, so expect sharp edges and read the code before you run it against anything you care about. Issues and pull requests are welcome.
Follow me on Github
A foundation you can always trust
❖ 86+ resolved cases across 70+ international clients, and the number that matters more than either is how many came back for a second engagement. Retesting is where you find out whether a report was read or filed.
❖ The work spans individuals, startups and enterprises, and the right assessment differs sharply between them. A startup with four engineers does not need the same report as a bank; handing them a 90-page document with 60 findings guarantees that none get fixed. Scope, depth and the shape of the remediation plan get set by what the team can realistically absorb.
❖ Two commitments hold across every engagement. Severities are not inflated — a Medium stays Medium, because burning credibility on a borderline High costs you the next genuine Critical. And nothing is reported that has not been reproduced, with the steps written out so your engineers can reproduce it too, and argue with me if I am wrong.
70+ satisfied clients worldwide
Essential Tools and Resources
The tools and sites I actually open during an engagement, for penetration testing, network analysis and malware work. Short list on purpose.