Skip to main content

How I Use Obsidian for Penetration Testing, CVE Hunting, and Studying

In the ever-evolving realm of cyber security, the tools and techniques at our disposal are as varied as the threats we aim to counteract. Among these tools, note-taking applications play a pivotal role, not just in organizing our thoughts but in streamlining our entire workflow. Today, I'm excited to share how Obsidian, a tool I embraced over two and a half years ago while preparing for my eJPT exam, has become an indispensable ally in my journey through penetration testing, CVE hunting, and continuous learning.

If you're not yet familiar with Obsidian, it's a robust note-taking application that operates on a local collection of plain text Markdown files. What sets it apart is its capability to interlink ideas, forming an expansive web of knowledge that is both intuitive and comprehensive to explore. Through considerable customization, I've developed what I consider to be an ideal method for consolidating notes, insights, and projects into a unified workspace. Here's a brief glimpse into my customized Obsidian setup:

Figure 1: Obsidian Vault Home Page

As you can see, there's a lot going on, so let's dive in.

How I Set Up My Obsidian

Navigating through over 600 pages of personal notes became increasingly overwhelming. My quest for a more efficient system led me to a game-changing YouTube tutorial on building a useful dashboard within Obsidian. This dashboard became the cornerstone of my organization, categorizing notes into specific domains like "Web Application Penetration Testing" and breaking them down into finer topics such as "Server-side Template Injection > Jinja."

Figure 2: Obsidian Vault Home Page Organization

Every new note begins its life on the dashboard, slotted into its appropriate subcategory. This not only makes note creation seamless but also ensures scalability. For new certifications, I craft a dedicated section on the dashboard, allowing me to focus solely on the exam material without distraction. My meticulous folder structure aids in potential migration to other apps, ensuring my notes remain organized.

Figure 3-4: Obsidian Vault Folder Structure

A separate "Media" folder keeps screenshots, videos, and audio files neatly organized, maintaining a clutter-free note-taking environment.

Managing CVE Hunting with Obsidian

CVE hunting is a passion I frequently share on LinkedIn, and Obsidian plays a crucial role in this endeavor. My CVE Hunting folder is meticulously organized into subfolders and includes an email template for contacting vendors about potential vulnerabilities.

Figure 5: Obsidian Vault CVE Hunting Folder

Upon discovering a vulnerability, I categorize it by application-bug name, moving it through folders from "Pending" to "Accepted/Rejected," and finally to "Disclosed" upon public disclosure. Below is the template I use for reporting vulnerabilities to vendors:


I am a security researcher. During an assessment,
I discovered a vulnerability in the <APPLICATION> application - specifically,
the Version: <VERSION>.

The vulnerability is a <VULNERABILITY> with CVSS:3.1 <CVSS STRING> & Base: <BASE>.

Below is a detailed replication guide.

1. Step 1

2. Step 2

3. ...

I would like to publicly disclose this vulnerability via a CVE,
but until then, waiting for your response.

Best Regards,

Searching My Write-Ups

As my vault grows, efficient search capabilities become paramount. Obsidian excels in this area, especially when leveraging tags and the Colorful Tags Plugin to categorize and beautify my notes.

Figure 6: Obsidian Vault Graph View

Figure 7: Obsidian Custom Tags

This tagging system is invaluable for navigating complex CTF write-ups that may span multiple attack vectors.

My Obsidian Theming

Finding the right theme took some time, but I've settled on AnuPpuccin, enhanced with the Styles Settings Plugin. The JetBrainsMono Nerd Font at size 12 ensures readability and aesthetic appeal in dark mode.

Figure 8: Obsidian Vault Theming

Essential Community Plugins

  • Callout Manager: For crafting custom callouts, adding visual interest and clarity to my notes.
  • Banners: To enhance the aesthetic appeal of my homepage.
  • Colorful Tags: For a visually appealing tagging system.
  • Dataviews: Allows for vault statistics visualization and advanced queries.
  • Embed Code Files: For directly viewing parts of enumeration scripts or exploits within notes.
  • Homepage: Ensures Obsidian opens to my meticulously organized dashboard.
  • Obsidian Git: To sync my vault with a private GitHub repository for backup and version control.
  • Style Settings: For customizing the AnupPuccin theme to my liking.
  • Templater: To create advanced templates, streamlining the note-taking and research process.

By integrating these elements, my Obsidian setup has become a fortress of knowledge, aiding in everything from certification preparation to the thrill of CVE hunting. Whether you're a seasoned security professional or just starting out, I hope this insight into my Obsidian workflow inspires you to organize your digital knowledge base in a way that fuels your passion and productivity.