Exposed SQL Dumps¶
Description¶
Detects publicly accessible MySQL dump files that may contain sensitive data.
Remediation¶
To remediate exposed SQL dumps, follow these steps:
- Immediately remove any publicly accessible SQL dumps from the server or storage location.
- Secure the storage location with proper access controls to prevent unauthorized access.
- Change any credentials that may have been exposed in the SQL dump.
- Review server logs to determine the scope of the exposure and identify any unauthorized access.
- Conduct a vulnerability assessment to understand how the SQL dumps were exposed and address the root cause.
- Implement regular monitoring to detect any future unauthorized access or exposure of sensitive data.
- Update your incident response plan to include steps for handling exposed data.
- Consider notifying affected users if any personal or sensitive information was compromised.
- Ensure that backups and dumps are encrypted and stored securely.
- Educate staff on best practices for data security and the importance of safeguarding backups.
Configuration¶
Identifier:
information_disclosure/exposed_sql_dumps
Examples¶
Ignore this check¶
Score¶
- Escape Severity:
Compliance¶
- OWASP: API8:2023
- OWASP LLM: LLM06:2023
- pci: 3.1
- gdpr: Article-32
- soc2: CC6
- psd2: Article-95
- iso27001: A.12.6
- nist: SP800-92
- fedramp: AC-22
Classification¶
- CWE: 200
Score¶
- CVSS_VECTOR: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CVSS_SCORE: 3.0