other
- Location
SKILL.md:31- Finding
Potential Disclosure of Sensitive Compliance Data to an External Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31-57,SKILL.md:100-126, andSKILL.md:185-188
Vulnerability Type: Sensitive Data Exposure
Risk Level: MediumVulnerable Documentation
The sample request encourages users to include internal audit findings and supporting evidence in the request:
json { "tier": "standard", "sessionId": "sess_20250117_audit_001", "controls": { "financial_reporting": [ { "controlId": "FR-001", "compliant": true, "notes": "Monthly reconciliation process documented and tested" }, { "controlId": "FR-002", "compliant": false, "notes": "Missing evidence of Q3 review sign-off" } ], "it_general_controls": [ { "controlId": "IT-101", "compliant": true, "notes": "Access reviews performed quarterly" }, { "controlId": "IT-102", "compliant": true } ] } }The documented endpoint accepts those values:
text ### POST /api/sox/assess **Description:** Perform comprehensive SOX compliance assessment across multiple control domains and sections. **Method:** POST **Path:** `/api/sox/assess`The documentation identifies an externally operated API route:
text ## References - **Kong Route:** https://api.mkkpro.com/compliance/sox-compliance - **API Docs:** https://api.mkkpro.com:8039/docsTechnical Analysis
The skill is designed to process organizational SOX assessment information, including control identifiers, compliance decisions, session identifiers, and free-form notes. The example specifically demonstrates transmitting details about a missing review sign-off, which may reveal an internal control deficiency.
The referenced service is hosted at
api.mkkpro.com, outside the local skill package. However, the documentation provides no warn ...[truncated 2144 chars]- Remediation
View remediation
Remediation Suggestions
- Clearly disclose that assessment content is transmitted to and processed by an externally operated service.
- Require explicit user or organizational approval before sending compliance data outside the local environment.
- Add prominent instructions prohibiting secrets, credentials, personal data, raw audit evidence, and unnecessary financial details in
notes. - Apply client-side redaction or data-loss-prevention checks before submission.
- Constrain the length and permitted content of
sessionId,controlId, section names, andnotes. - Document the service's data retention, deletion, encryption, access-control, residency, incident-response, and secondary-use policies.
- Provide a self-hosted or organization-approved endpoint option for sensitive assessments.
- Minimize transmitted data by using standardized finding codes instead of free-form evidence wherever possible.
- Establish contractual safeguards and verify that third-party handling is compatible with the organization's SOX, privacy, and vendor-risk requirements.
