Home / SecWiki: a security reading list

SecWiki: a security reading list

Updated Nov 2026

SecWiki began as a community link board where readers shared articles and tools they had found useful. That board is closed. Nothing is submitted, voted on or ranked any more, and the old listings have not been carried over.

This page takes its place as a curated reading guide. It is updated slowly and by hand, and it describes where to start in each area rather than listing every link ever shared. Where the archive has related notes, the categories below point to them.

Categories

  • Web security. Injection, cross-site scripting, browser policy quirks and server-side mistakes. Start with the web security notes.
  • Penetration testing. Scoping, reconnaissance, enumeration and reporting. Good material here explains method and evidence, not just tool names.
  • Malware. Behaviour analysis, unpacking and attribution basics. Read these with a sandbox mindset and never run samples on a machine you care about.
  • Forensics. Disk, memory and network artefacts, and how to preserve them. Timelines and careful notes matter more than any single tool.
  • CTF. Competition challenges are a safe way to practise. The CTF write-ups walk through how challenges were approached and solved.
  • Radio and SDR. Software-defined radio, signal capture and protocol decoding. See the hardware security section for related wireless and device work.
  • Mobile. App sandboxing, insecure storage, weak transport security and platform permission models on Android and iOS.
  • Firmware. Extracting, unpacking and inspecting embedded images, and finding debug interfaces. Again, hardware security is the best entry point.
  • Reverse engineering. Reading binaries, recovering logic and understanding file formats. The reverse engineering notes cover disassembly and analysis workflows.
  • Fuzzing. Feeding programs unexpected input to expose crashes, and triaging what comes out. Coverage guidance and good seed corpora are the ideas to learn first.
  • Exploit development. Memory corruption, mitigations and how they are bypassed or defeated. The kernel and exploits section is the place to read next.
  • Defence. Hardening, detection, logging and incident response. Most attack write-ups end with a lesson for defenders, and that lesson is often the most useful part.

Longer reading

For longer, citable material such as conference papers and academic work, see the papers collection. It is a better starting point than a news-style feed when you want depth.

How to use this guide

Pick one category, read two or three items in full, and try to reproduce or explain the key idea in your own words. That habit teaches more than collecting bookmarks. The guide is reviewed and updated by the editors from time to time.