HavocSec
Brand guidelines for media, collaborations, and community use.
Brand Identity
Who We Are
HavocSec is a cybersecurity content studio for penetration testers, CTF players, red teamers, and anyone who learns by breaking things. We publish detailed writeups, walkthroughs, and technical guides that teach real-world offensive security.
Who We Serve
Security researchers, bug bounty hunters, students learning pentesting, CTF competitors, and the professionals who need to understand how attackers think. Our readers want depth, not summaries.
What We Reject
Marketing fluff. Clickbait thumbnails. Surface-level "top 10" lists. Gatekeeping. Paywalled knowledge that should be free. We write for the community, not for engagement metrics.
The Name
"Havoc" represents controlled chaos - the deliberate disruption of systems to understand them. "Sec" grounds it in security. Together: break with purpose, secure with knowledge.
Logo System
Primary - Dark Background (Preferred) On Light Background On Pure Black On Dark Gradient Clear Space & Minimum Size
- Maintain clear space equal to the height of the "H" on all sides of the logo
- Minimum size: 32px height for digital, 12mm for print
- Never crowd the logo with other elements, text, or borders
- The logo should always be the most prominent brand element in any composition
Logo Misuse - Never Do This
- Never stretch, skew, rotate, or distort the logo proportions
- Never recolor the logo with unapproved colors (no rainbow, no gradient fills)
- Never place on busy photographs or low-contrast backgrounds
- Never add drop shadows, outer glows, bevels, or 3D effects
- Never outline or stroke the logo
- Never animate the logo without explicit approval
- Never crop or partially obscure any part of the logo
- Never recreate the logo in a different typeface
Color Palette
#39FF14 rgb(57, 255, 20) hsl(110, 100%, 54%) #0A0F1A rgb(10, 15, 26) #0F172A rgb(15, 23, 42) #1E293B rgb(30, 41, 59) #E2E8F0 rgb(226, 232, 240) #64748B rgb(100, 116, 139) Color Combinations & Contrast
The Green Rule
- Havoc Green is an accent, not a surface. It should never exceed 15% of any composition
- Use it for: interactive elements, highlights, code accents, borders, and emphasis
- Never use it as a full background color
- Never use it for body text - only headings, labels, and accents
- On light backgrounds, darken to #2dd40f for adequate contrast
Typography
Type Scale
| Element | Size | Weight | Tracking |
|---|---|---|---|
| H1 — Page Title | 2.5rem | 800 | -0.02em |
| H2 — Section | 1.75rem | 700 | -0.015em |
| H3 — Subsection | 1.25rem | 700 | -0.01em |
| Body | 1rem | 400 | 0 |
| Code Block | 0.9rem | 400 | 0 |
| Caption / Meta | 0.8rem | 500 | 0.02em |
| Badge / Label | 0.65rem | 900 | 0.12em |
Iconography
Spacing & Layout
Layout Specifications
| Property | Value | Context |
|---|---|---|
| Max content width | 900px | Article body |
| Container padding | 1.25rem | Mobile edges |
| Card border-radius | 10px — 16px | Cards, modals |
| Button border-radius | 6px — 999px | Buttons, pills |
| Border width | 1px — 1.5px | Cards, inputs |
| Border color | rgba(57,255,20, 0.2) | Accent borders |
Voice & Tone
Direct & Technical
No fluff. Say what needs to be said. Technical accuracy over marketing speak. If it takes 3 words, do not use 30.
Educational
Break to understand. Build to endure. Every writeup teaches something real. Explain the "why" not just the "how."
Community-First
For the community. Knowledge shared is knowledge multiplied. We write so others can learn, not to show off.
Hacker Mindset
Curiosity-driven. Question everything. Verify assumptions. Show your work. The methodology matters as much as the result.
Respect the Reader
Assume intelligence. Never condescend. If they already know something, let them skip ahead. No "In this blog post, we will be discussing..."
No Theater
The bug is here. Here is the fix. Here is what we learned. No "You won't BELIEVE what this hacker found..." energy. Ever.
Content Formatting Rules
Writing Style
- Active voice. Present tense for instructions
- Second person ("you") for tutorials and guides
- Short paragraphs. One idea per paragraph
- Code blocks for every command - never inline a full command
- Explain flags and arguments in commands
- Include expected output where helpful
- Tips in blockquotes with
> **Tip:**prefix
Formatting Conventions
- Headings: sentence case, not title case
- File paths and commands in
backticks - Tool names capitalized as the tool does (Nmap, Hashcat, Burp Suite)
- CVE IDs always in format
CVE-YYYY-NNNNN - IP addresses use
10.129.x.xfor targets - Screenshots after the step they illustrate, not before
- Tables for structured data (ports, credentials, tools)
Writeup Structure
- Overview with attack chain mermaid diagram
- Enumeration → Foothold → PrivEsc flow
- Each step numbered and self-contained
- Lessons Learned section at the end
- Sign-off:
HavocSec - for the community. - Tags: platform, OS, CVE, techniques, difficulty
What We Never Write
- No "In this blog post, we will discuss..."
- No "Without further ado..."
- No clickbait titles or ALL CAPS excitement
- No unexplained jargon without context
- No screenshots without explanation
- No steps that assume tools are installed without noting it
Taglines & Headlines
"Break to understand. Build to endure."
Social & Applied Surfaces
Do's & Don'ts
✓ Do
- Use the logo with adequate clear space on all sides
- Reference as "HavocSec" (one word, capital H and S)
- Link back to havocsec.com when sharing content
- Use the green accent sparingly on dark backgrounds
- Credit the author (Havoc) when quoting writeups
- Use dark mode as the default presentation context
- Maintain the editorial, technical tone in any co-branded content
- Use monospace for any code, commands, or technical references
- Keep compositions clean with generous whitespace
- Use the brand in CTF team contexts and security community events
- Share writeup links freely - that is what they are for
- Use screenshots from the site with visible attribution
✗ Don't
- Alter the logo colors, proportions, or add effects
- Use the brand to imply endorsement of products or services
- Reproduce full writeups without written permission
- Use Havoc Green on light/white backgrounds without darkening it
- Remove attribution from shared or embedded content
- Use the brand in any context promoting illegal activity
- Add gradients, shadows, or glows to the logo
- Use Comic Sans, Papyrus, or any novelty font alongside the brand
- Place the logo smaller than 32px height
- Use the brand on busy photographic backgrounds
- Combine with other brand logos in a way that implies partnership without agreement
- Use retro-gaming pixel fonts, matrix code rain, or hooded-hacker stock imagery
- Create derivative logos or "inspired by" versions
- Use the brand name in domain names or social handles without permission
License & Usage
All HavocSec content is published under Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International. The brand assets on this page are provided for reference and approved use cases only.
- You may share and link to content with proper attribution
- You may use the logo when referencing HavocSec in editorial contexts
- You may not use brand assets for commercial purposes without written permission
- You may not create derivative works from the logo or brand materials
- You may not use the brand in any way that implies official endorsement
For collaboration, media inquiries, or brand usage questions: Contact Havoc