MuleSight Security Policy
| Owner | Flowdence Security and Engineering |
| Applies to app | MuleSight for Confluence |
| Review cadence | Quarterly and after security-significant changes |
1. Security design principles
Section titled “1. Security design principles”- Least privilege on app scopes and egress.
- Secure secret storage with no hardcoded credentials.
- Cache-first resilience without exposing sensitive material.
- Structured logging with redaction.
2. Access and authorization model
Section titled “2. Access and authorization model”- Global configuration writes are context-guarded.
- Data fetches are constrained to configured MuleSoft org and environment inputs.
- Mutating config actions are routed through resolver functions with controlled entry points.
3. Secret management
Section titled “3. Secret management”- MuleSoft client secret and OAuth token are stored in Forge secret storage.
- Token cache invalidation occurs on auth context changes and 401 retry flows.
4. Data egress and network controls
Section titled “4. Data egress and network controls”- Outbound fetch is restricted to MuleSoft endpoint(s) declared in manifest.
- No broad wildcard egress is configured.
5. Logging policy
Section titled “5. Logging policy”- Logs are structured and redacted for keys resembling tokens/secrets/passwords/authorization.
- Operational errors are captured without dumping raw secret values.
6. Vulnerability and patch management
Section titled “6. Vulnerability and patch management”- Security defects are triaged by severity and tracked to remediation.
- Marketplace security requirement timelines are treated as release constraints.
7. Incident response
Section titled “7. Incident response”- Incident process and communication standards are defined in operational runbooks.
- Security escalation contact:
security@flowdence.io.
8. Shared responsibility references
Section titled “8. Shared responsibility references”MuleSight operates on Forge infrastructure; platform and app responsibilities are split per Atlassian shared responsibility guidance.
9. MuleSight-specific controls
Section titled “9. MuleSight-specific controls”MuleSight’s highest-risk materials are MuleSoft connected-app secrets, OAuth token material, cached operational snapshots, and diagnostics results. Secrets and token material are stored in Forge secret storage. Dataset caches are keyed by product context and refreshed through controlled resolver paths.
Outbound network access is restricted to Anypoint endpoints required for product behavior. Required OAuth scopes are documented in configuration and diagnostics surfaces so customers can identify missing, partial, or excessive scope coverage. Structured logs redact token-like and secret-like values and avoid dumping raw Anypoint responses when reporting supportable errors.
10. Shared baseline policies
Section titled “10. Shared baseline policies”This app-specific policy is read together with the shared Flowdence baseline: