You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+50-1Lines changed: 50 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,18 @@ The SOC-2 compliance solution for the discerningly paranoid security engineer.
4
4
5
5

6
6
7
+
## What Happens When a Security Engineer Builds an MDM
8
+
9
+
gitMDM is what you get when you ask a security engineer to make an MDM tool. Traditional MDMs operate on the assumption that the central server is trustworthy and should have root access to execute arbitrary code on all endpoints. We think that's insane.
10
+
11
+
**Core Security Principle**: A compromise of the MDM server should NOT result in a compromise of all agents reporting to it.
12
+
13
+
This is why gitMDM:
14
+
-**Cannot execute remote commands** - The server literally lacks the code to push commands to agents
15
+
-**Uses cryptographic signatures** - All agent configurations are signed with Sigstore, preventing a compromised server from injecting malicious checks
16
+
-**Runs without privileges** - Agents run as regular users, not root/SYSTEM
17
+
-**Reports only** - Information flows one way: from agents to server, never the reverse
18
+
7
19
## Your Problem
8
20
9
21
Your startup just hit the enterprise sales milestone where someone asks "are you SOC 2 compliant?" Meanwhile, your engineering team runs OpenBSD on ThinkPads, Arch on Frameworks, and that one person still dailying Plan 9.
@@ -25,6 +37,7 @@ Your Team: "...continue"
25
37
### Why Your Security Team Will Actually Approve This
26
38
27
39
-**Zero Remote Execution**: Can't push commands or install software. The server only receives data.
40
+
-**Cryptographically Signed Configs**: All agent configurations require Sigstore signatures. A compromised server can't inject malicious checks.
28
41
-**No Auto-Updates**: No downloading binaries from the internet. Updates require YOU to rebuild and redeploy.
29
42
-**Runs as User**: No root, no SYSTEM. Can't execute arbitrary code or modify your system.
30
43
-**You Own Everything**: Your server, your git repo, your data. No third-party cloud with root access to your fleet.
@@ -102,11 +115,47 @@ We detect 11+ desktop environments because your team refuses to standardize.
102
115
103
116
The server literally cannot execute commands. We removed the code. It's not there.
104
117
118
+
### Configuration Integrity via Sigstore
119
+
120
+
Every agent configuration is cryptographically signed using Sigstore's keyless signing:
0 commit comments