Skip to content

Commit 189b74d

Browse files
authored
Merge pull request #6 from codeGROOVE-dev/tstromberg-patch-1
Clarify osquery limitations
2 parents 80eabe2 + a37313f commit 189b74d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ We love Google Cloud Run for our deployment story - check out `./hacks/deploy.sh
9292
Attackers can read compliance reports and delete them. That's it. They cannot push commands, install software, or access agent machines.
9393

9494
**Why not just use osquery?**
95-
osquery is a great platform to build an MDM on top of, but its cross-platform support is limited.
95+
We ❤️ osquery – enough that we previously created [osquery-defense-kit](https://github.com/chainguard-dev/osquery-defense-kit) - but it's only part of an MDM solution, and didn't meet our goals when it came to platform support & operating with low privilege.
9696

9797
**How do you prevent supply chain attacks?**
9898
Agents are built from source, checks are compiled in, and with Sigstore integration, all configurations are cryptographically signed with identity verification. Minimal dependencies.

0 commit comments

Comments
 (0)