Skip to content

Home

Overview

This set of guidelines is designed to ensure that software development, and infrastructure projects are secure from the outset, reducing the risk of vulnerabilities, insider threats and generally following the assume breach mindset.

Non-security code styles and design patterns are also included in each set of guides to ensure that code is consistent, and readable. Readability is meant to encompass people from a non-technical background (but with an expectation of logical thought) as well as LLMs.

Credentials

Why should you trust me? That is not for this site to go in-depth over, check out this one instead:
https://elliot.huffman.me

Please select a system to learn more about it:

  • General/Shared

    Constant concepts and patterns to use across all systems/projects.

    Overview

  • TypeScript

    TypeScript/JavaScript language best practices and recommended style guides.

    Getting started

  • GitHub (Coming soon!)

    GitHub Enterprise, Org, Repo, and Infrastructure best practices.

  • PowerShell (Coming soon!)

    PowerShell language best practices and recommended style guides.

  • Azure (Coming soon!)

    Azure Security Best Practices and recommended governance.

Why the choice in name?

I started with the acronym SSE from the CPU instruction set called SSE (Streaming SIMD Extensions). Then I worked backward to a logical name for the project. I am a nerd, what can I say? 🤓