Skip to content

About

Collection of insights and recommendations gathered from my time working in security.

Topics

Resources

Stars

2 stars

Watchers

1 watching

Forks

Latest commit

 

History

35 Commits

Folders and files

Repository files navigation

AppSec/ProdSec Reference

Curated notes on application and product security: design, assessment, operations-adjacent engineering, supply chain, and LLM risks. Written for practitioners who want checklists and patterns, not a vendor pitch.

Goal: If this helps someone ship safer software or pass a better interview loop, it did its job.


Disclaimer

Important notice:
This repository reflects personal study and practice, not the policies, standards, or requirements of any employer, client, or school - past or present.

Material is provided as-is. Security changes daily; errors and stale detail are possible. Use at your own risk and validate against your own context. Nothing here is legal, regulatory, or HR advice.


License

Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0). See LICENSE.


Career context

Hiring is uneven, timelines are long, and many teams run on tight budgets. If you are navigating that while reading technical references, see career-outlook.md. For resume layout ideas and a fictional anonymized example, see resume-guide-and-generic-example.md.


Repository name

appsec-prodsec-reference still fits this collection: it is about securing what you build (AppSec) and how security shows up in the product lifecycle (ProdSec). You do not need a new repository for that scope.

Rename only if you want a broader umbrella (for example personal blog, non-security topics, or multiple programs in one repo). Renaming on GitHub preserves redirects for a time but breaks bookmarks eventually - prefer a stable name and use the companion repo for intake.


Contents

Companion repository

This repo centers on software you build; the companion centers on software you run.


Usage

Fork or clone, then adapt. No single reference fits every org, regulator, or stack. Prefer small, verifiable changes over copying long policies wholesale.


Publishing

If you mirror this work to GitHub with a scrubbed history and release tags, see PUBLISHING.md.

About

Collection of insights and recommendations gathered from my time working in security.

Topics

Resources

Stars

2 stars

Watchers

1 watching

Forks

Used by

Contributors