in-toto VS macOS-Security-and-Privacy-Guide

The things you mentioned are not solved by a typical "SBOM" but e.g. CycloneDX has extra fields to record provenance and pedigree and things like in-toto (https://in-toto.io/) or SLSA (https://slsa.dev/) also aim to work in this field.

I've spent the last six months in this field and people will tell you that this or that is an industry best practice or "a standard" but in my experience none of that is true. Everyone is still trying to figure out how best to protect the software supply chain security and things are still very much in flux.

in-toto is an open source project that focuses on the attestation part of software supply chain security. You use it to define a “layout” for a project, i.e., how the different components should fit together. A project ships this definition with its code, and then another user of that software can compare what they have with the attached definition to see if it matches the structure and contents they expect. If it doesn’t, then this could point to external tampering or other issues.

But it's not all doom and gloom because the industry is evolving. Companies like Google are formulating tools like scorecard to heuristically reduce risk by encouraging you to rely on trustable dependencies only. There's also more complex tools like in-toto that actually look at the integrity of your supply chain (don't ask me how this one works, I just know that people like it).

Hi friends, I followed this guide: https://github.com/drduh/macOS-Security-and-Privacy-Guide and some additional steps to protect my macbook from being accessed by unauthorized people. The key steps I did was a full disk encryption and a custom firmware password. This makes it extremely difficult to repurpose my macbook after for example a theft. The reason I want this is that I often study in university or sometimes work in public places, but I also work as a software developer with sensitive consumer data.

https://github.com/drduh/macOS-Security-and-Privacy-Guide/is...

turn on FileVault , turn on the firewall (built in). install Lulu firewall follow this guide and harden the system https://github.com/drduh/macOS-Security-and-Privacy-Guide

I'm looking for a guide to harden MacOS Ventura, preferably including little snitch/lulu blocklist suggestions for MacOS services. I'm aware of dr druh's guide (that currently doesn't seem to be updated for Ventura though) and isn't including a little snitch/lulu blocklist.

- macos, following https://github.com/drduh/macOS-Security-and-Privacy-Guide for hardening (I haven't compared this to other hardening guides, but doing something is better than nothing)

I remember seeing this, I have never followed it so I don't know what it's worth but it's seems quite comprehensive