My cybersecurity journey started from the inside out — building secure products in my Computer Science degree, and now deepening that understanding through a Master's in Cybersecurity at Swinburne University / Barzan University College, Doha.
I don't just study security in theory — I've responded to a real-world website compromise, conducted structured plugin vulnerability audits, and remediated live threats on production systems without service disruption.
I believe security is most powerful when it's baked into the design process from the start — not bolted on at the end. That's the lens I bring to every digital product I build or maintain.
$ whoami
Ameera Khan — Cybersecurity Graduate Student
$ cat qualifications.txt
MSc Cybersecurity (In Progress) — Swinburne / Barzan UC
BSc Computer Science — GPA 9.75/10
CISCO: Introduction to Cybersecurity ✓
$ ls ./skills/
network_security/
incident_response/
secure_coding/
data_privacy/
risk_management/
wordpress_hardening/
$ cat notable_incident.log
[RESOLVED] Live WordPress compromise detected
Root cause: Unpatched outdated plugins
Action: Malware removed, plugins audited & updated
Downtime: 0 minutes
$ # Status: Ready for the next challenge
█
Real-world security work and applied cybersecurity projects.
Shortly after joining ILM Education, I noticed something unusual on the live website: random words appearing mid-sentence, all hyperlinked to an unknown Ukrainian domain. This was not a design choice — the site had been compromised through outdated, unpatched WordPress plugins.
1. Verified issue across multiple browsers and devices (ruled out local glitch)
2. Audited WordPress dashboard login and activity logs
3. Identified compromised entry point: outdated/expired plugins
4. Removed all malicious embedded links from the live codebase
5. Deleted all unused and expired plugins from the installation
6. Updated every active plugin to its current, patched version
7. Verified clean state across all pages post-remediation
Outdated plugins are one of the most common WordPress attack vectors. Unpatched vulnerabilities give attackers a persistent, low-visibility entry point. Regular plugin audits are essential maintenance — not optional.
🏆 Award Winner
As the architect of GenRx — a personalised medicine recommendation platform — I designed the application with privacy-by-design principles from the ground up. Health applications handle sensitive PII (Personally Identifiable Information) and require careful thought about data minimisation, consent flows, and secure data handling.
Thesis Project
My final-year thesis project — a full Learning Management System (LMS) prototype built on ReactJS and Firebase — incorporated security considerations throughout the development lifecycle. As a system handling student data and educational records, securing both the data layer and the access controls was a core requirement.
Barzan University College · Swinburne University of Technology, Doha
Focus: Secure digital infrastructure, risk management, data privacy, compliance frameworks, network security, and advanced threat analysis.
CISCO Networking Academy
Foundations of cybersecurity: threat landscapes, common attack types, defence strategies, and the role of security professionals in modern organisations.
MIE–SPPU, Doha, Qatar · Highest Academic Scorer · Scholarship
Core CS curriculum including data structures, algorithms, networks, databases, and software engineering — forming the technical foundation for applied security work.
CISCO Networking Academy
Data analysis and interpretation skills that support security analytics, log analysis, and threat pattern recognition.
Key takeaways from real-world security work and ongoing studies.
The ILM Education compromise was enabled entirely by outdated plugins. A regular update and audit cadence would have closed the window before it was exploited. Most breaches exploit known vulnerabilities — not zero-days.
Retrofitting security onto an existing system is always harder and more expensive than designing it in from the start. Privacy-by-design isn't just a compliance checkbox — it's a philosophy that saves significant remediation effort later.
When a system is compromised, working systematically from the outside in — verifying scope, then identifying root cause before remediation — prevents both missing things and breaking things. Speed without structure makes incidents worse.
Technical controls are only as effective as the people operating them. Security awareness, clear processes, and a culture that reports anomalies without fear are as important as any firewall.
You cannot lose data you never collected. Designing systems to collect only what's necessary — and handling it with appropriate controls — is both a privacy best practice and a security risk reduction strategy.
Plugins, libraries, and third-party integrations expand your attack surface beyond your own code. Every dependency is a potential vector. Regular audits, minimal permissions, and keeping the dependency count lean all reduce exposure.
Open to cybersecurity roles, research collaborations, and security consulting projects. Let's build something that's not just functional — but genuinely secure.