Comparison Overview
Pentagon Force Protection Agency

Pentagon Force Protection Agency
9000 Defense Pentagon, Washington, 20301-0001, US
Last Update: 02/04/2026
Pentagon Force Protection Agency is a civilian Defense Agency within the Department of Defense. Our law enforcement officers protect and safeguard the occupants, visitors, and infrastructure of the Pentagon and associated facilities, including the Mark Center and Defens...

SAPS
ZA
Last Update: 08/09/2026
Policing in South Africa. I am attached to the newly formed Directorate for Priority Crime Investigations. Formally I was attached to the Detecitve Service and have been conduction investigations for over 25 years. I have also been attached to the National Inspectorate ...
Compliance Ranges Comparison

Pentagon Force Protection Agency







SAPS






Benchmark & Cyber Underwriting Signals
Incidents vs Law Enforcement Industry Avg (This Year)
No incidents recorded for Pentagon Force Protection Agency in 2026.
Incidents vs Law Enforcement Industry Avg (This Year)
SAPS has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Pentagon Force Protection Agency (X = Date, Y = Severity)
Pentagon Force Protection Agency cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SAPS (X = Date, Y = Severity)
SAPS cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Pentagon Force Protection Agency

SAPS
FAQ
Latest Global CVEs
knowns versions before 0.30.0 contain an authorization bypass vulnerability where mutating code actions are incorrectly classified as read-only operations. Attackers with read-restricted sessions can exploit code.replace to modify permission configurations and escalate privileges on subsequent calls.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/permissions/guard.go#L44-L60
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/permissions/registry.go#L99-L140
- https://github.com/knowns-dev/knowns/commit/a2c98fc5c313463576c9348beeec6a74ddd7333b
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-w323-3wpx-f7g5
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-authorization-bypass-via-misclassified-code-actions
knowns versions before 0.30.0 serve the management API without authentication on all network interfaces by default, with no password required on fresh installations. Attackers can access the unauthenticated /api/tunnel/start endpoint to provision a public tunnel and republish the API at a publicly accessible address.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/cli/browser.go#L193-L200
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/auth.go#L80-L86
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/tunnel.go#L26-L38
- https://github.com/knowns-dev/knowns/commit/878a02cb7cc14f0a592fdfda7a520af3cac500fb
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-fc85-99vc-9c75
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-unauthenticated-management-api-exposure
knowns before 0.30.0 fails to validate import names in the import routes, allowing unauthenticated attackers to write files outside the imports directory. Attackers can supply traversal sequences in the name parameter to escape the imports directory and overwrite arbitrary files writable by the server process.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/imports.go#L376-L420
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/imports.go#L519-L551
- https://github.com/knowns-dev/knowns/commit/d3989829fb5095666d23d005b2f78a082832a396
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-wh3c-v55g-qfg8
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-import-name
knowns versions before 0.30.0 contain a path traversal vulnerability in the handleCodeReplace() function that allows attackers to overwrite arbitrary files outside the project root. Attackers can supply absolute paths or relative paths containing directory traversal sequences to write malicious content to sensitive files like shell startup scripts or SSH configuration files.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/mcp/handlers/code.go#L588-L646
- https://github.com/knowns-dev/knowns/commit/a2c98fc5c313463576c9348beeec6a74ddd7333b
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-f539-xgc6-xw7q
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-code-replace-mcp-action
knowns versions before 0.30.0 fail to validate the settings.lsp.languages binary field in project configuration files, allowing attackers to execute arbitrary binaries by crafting a malicious .knowns/config.json file. When a repository with a crafted configuration is opened, the unvalidated binary path is executed twice under the user's account without any verification.
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/lsp/detect.go#L128-L157
- https://github.com/knowns-dev/knowns/blob/v0.29.1/internal/models/config.go#L205-L216
- https://github.com/knowns-dev/knowns/commit/d3989829fb5095666d23d005b2f78a082832a396
- https://github.com/knowns-dev/knowns/releases/tag/v0.30.0
- https://github.com/knowns-dev/knowns/security/advisories/GHSA-mc52-mwq4-vfx3
- https://www.vulncheck.com/advisories/knowns-before-0.30.0-arbitrary-code-execution-via-lsp-binary