Home Lab Network Map
Documenting a small virtual lab with Nmap: finding hosts, open ports and services on machines I own, then writing what each result means.
Learning • Building • Researching
> Faizan Ahm3d
I Study Systems. I Observe Patterns. I Think Beyond the Obvious.
Cybersecurity, human behaviour, and the science of digital trust.
No ads or trackers in this site's code · Progress stays on your device
faizan@lab: ~
// 01 — about
About Faizan Ahm3d
I'm a cybersecurity learner fascinated by two questions: how do systems actually work, and how do people actually behave around them? I study both, because most real-world security stories involve technology and humans together.
I'm early in this journey. I practise only on machines I own, intentionally vulnerable apps, and platforms that allow testing. This site lists no employers or clients, and I will add credentials only after I have genuinely earned them.
- Focus Security fundamentals and human behaviour
- Studying Linux, networking, web security
- Lab tools Nmap and Burp Suite Community (authorized targets only)
- Ethics Permission first, always
- Credentials None listed yet
// 02 — toolkit
Cybersecurity Skills
Green means actively practising. Amber means early learning. This is an honest snapshot, not a claim of expertise.
// web security
Burp Suite Community practising HTTP fundamentals practising OWASP Top 10 learning Authentication & sessions learning// networking
Nmap (own lab) practising TCP/IP, DNS basics practising Wireshark learning Network segmentation learning// systems
Linux command line practising Bash basics practising File permissions learning Python scripting learning// human-centred security
Clear note-taking & writing practising Social-engineering awareness (defensive) learning Behavioural psychology basics reading Threat modelling learning// 03 — lab work
Projects & Authorized Labs
Placeholder projects: edit titles and text to match what you actually build. Every target is my own lab machine or an intentionally vulnerable practice app.
Burp Suite × DVWA Practice Notes
Using Burp Suite Community against a local DVWA install to learn how input handling issues look in HTTP traffic, with a defender's fix for each one.
Security Knowledge Base
The articles, fact cards and learning path on this page, built as a single static file with no frameworks and no trackers.
Intent vs Evidence Reading Notes
A reading journal on why behaviour is ambiguous and how defenders reason carefully when evidence is incomplete.
// interactive lab
Mini-Challenge: The Hidden Note
A harmless, simulated Linux-style terminal that runs entirely in your browser. It touches no real system. Goal: find the flag (it looks like FLAG{...}) and submit it with submit FLAG{...}.
guest@lab: simulated environment
Flag not found yet
// 04 — capture the flag
CTF Write-ups
Templates to replace with your own write-ups. Check each platform's rules first, because many do not allow public solutions for active challenges.
Template: Beginner Web Challenge
Goal: What was the challenge asking you to find?
- Recon: What did you observe (pages, parameters, headers)?
- Hypothesis: What weakness did you suspect, and why?
- Result: What did you learn?
- Defender's fix: How would a developer prevent this?
Focus on your thinking process and the defensive lesson, and publish only where the platform allows it.
Template: Linux Fundamentals Room
Summarise the commands you practised and what each taught you about files and permissions.
$ ls -la $ find . -name "*.txt" $ chmod 600 notes.txt
Template: Network Scanning in My Own Lab
Explain a scan of your own lab VM and how to read the output.
$ nmap -sV <your-lab-vm-ip>
Only scan systems you own or have explicit written permission to test.
// 05 — knowledge base
Security Knowledge Base
Short, useful notes written for beginners. Reveal a fact, read an article, or follow the learning path at your own pace.
Continue Learning
Articles read0/0
Learning path stages complete0/0
Click-to-reveal security facts
Articles
Beginner learning path
Six stages. Select a stage to open it, then mark it complete when you're ready.
// 06 — intelligence lab
Human Behaviour Lab
An educational space about how people behave around technology. It is built on one principle: you cannot reliably read a person's intentions from a single gesture, click or pause.
Why intent can't be read from one behaviour
- One action, such as a pause or a click, has many possible explanations: habit, distraction, accessibility needs, culture or mood.
- Careful analysis uses context and several signals, and even then deals in probabilities rather than certainty.
- Ethical behaviour research needs consent. That is why everything here is opt-in, local and visible to you.
Step 1: Choose your interests
Voluntary. Pick any topics you like. They only change the suggestions below.
Step 3: Suggested reading
Step 2: Reflection quiz
Privacy & controls
Nothing on this page is sent to a server. No camera, microphone, fingerprinting or cross-site tracking is used. By default your choices live only in memory and disappear when you refresh.
// 07 — intelligence notes
Intelligence Notes
Short thinking notes on evidence, patterns and uncertainty. These are placeholder drafts: edit or replace them with your own writing.
Pattern is not proof
Seeing a pattern is the start of an investigation, not the end of one. A good analyst asks what else could produce the same pattern, and what evidence would change their mind.
Threat modelling in one question
What are we protecting, and from whom? Starting from that question keeps security work focused on real risks instead of every possible one.
Base rates: why rare things stay rare
If something is rare, even a good detector will raise many false alarms. Remembering base rates helps defenders avoid over-reacting to weak signals.
Curiosity with boundaries
Curiosity drives learning in security, but authorization defines what is acceptable. Test only what you own or have explicit permission to test, and respect people's privacy as you learn.
// 08 — contact
Contact
Questions, study-group ideas, or feedback on my notes? I'd be glad to hear from you.
Email: you@example.com
Why there's no contact form
A form that really delivers messages needs a backend service, which this static site deliberately avoids. An email link is simple, private and reliable. This site has no logins, no accounts and no password fields.