Skip to main content
Data protection in MuBit has two layers: route policy controls external lane access, and ACL controls node-level visibility. If your team treats guardrails as a late-stage concern, failures usually appear first in production as policy denials or unexpected visibility. Define direct-lane policy and ACL ownership early. Then enforce those choices in code paths and operational runbooks.

​
Guardrail layer 1: route policy

  • /v2/core/health and /v2/core/auth/* are always available.
  • /v2/core/search requires MUBIT_CORE_ENABLE_DIRECT_SEARCH.
  • Other external /v2/core/* routes are denied by default middleware.

​
Guardrail layer 2: ACL operations

RoutePurpose
POST /v2/core/acl/grantGrant read/write/delete permissions
POST /v2/core/acl/revokeRemove permissions
POST /v2/core/acl/checkVerify permission state

​
Failure modes and troubleshooting

SymptomRoot causeFix
Direct method deniedLane policy offUse routed control query or enable lane intentionally
Unexpected visibilityACL model incompleteValidate grant/revoke/check flow
Broad blast radiusPolicies enabled globallyRoll out lane flags per environment

​
Next steps