|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Reporting a Vulnerability |
| 4 | + |
| 5 | +If you discover a security vulnerability in this project, please report it responsibly. **Do not open a public GitHub issue for security vulnerabilities.** |
| 6 | + |
| 7 | +### How to Report |
| 8 | + |
| 9 | +1. **Email**: Send a detailed report to **security-opensource@gruposantander.com** |
| 10 | +2. **GitHub Security Advisories**: Alternatively, use [GitHub Security Advisories](../../security/advisories/new) to report privately. |
| 11 | + |
| 12 | +### What to Include |
| 13 | + |
| 14 | +- Description of the vulnerability |
| 15 | +- Steps to reproduce |
| 16 | +- Potential impact |
| 17 | +- Suggested fix (if any) |
| 18 | + |
| 19 | +### Response SLA |
| 20 | + |
| 21 | +| Stage | SLA | |
| 22 | +|:---|:---| |
| 23 | +| Acknowledgment of report | < 48 hours | |
| 24 | +| Initial assessment and severity classification | < 7 days | |
| 25 | +| Fix for Critical/High severity | < 30 days | |
| 26 | +| Fix for Medium/Low severity | < 90 days | |
| 27 | + |
| 28 | +### What Happens Next |
| 29 | + |
| 30 | +1. We will acknowledge your report within 48 hours. |
| 31 | +2. We will investigate and determine the severity. |
| 32 | +3. We will develop and test a fix. |
| 33 | +4. We will release the fix and publish a security advisory. |
| 34 | +5. We will credit you publicly in the advisory and CHANGELOG (unless you prefer to remain anonymous). |
| 35 | + |
| 36 | +## Scope |
| 37 | + |
| 38 | +This security policy applies **only** to code in this repository. It does not cover: |
| 39 | + |
| 40 | +- Santander's internal infrastructure or systems |
| 41 | +- Other Santander products or services |
| 42 | +- Third-party dependencies (report those to the respective maintainers) |
| 43 | +- The third-party German Credit dataset (not redistributed here; see `data/README.md`) |
| 44 | + |
| 45 | +## Supported Versions |
| 46 | + |
| 47 | +| Version | Supported | |
| 48 | +|:---|:---| |
| 49 | +| Latest release | Yes | |
| 50 | +| Previous minor release | Security fixes only | |
| 51 | +| Older versions | No | |
| 52 | + |
| 53 | +## Security Best Practices for Contributors |
| 54 | + |
| 55 | +- Never commit secrets, API keys, tokens, or credentials |
| 56 | +- Never commit internal URLs, IP addresses, or corporate email addresses |
| 57 | +- Never commit personally identifiable information (PII) or customer data |
| 58 | +- Never commit the German Credit dataset or any other third-party data |
| 59 | +- Use environment variables for any configuration that could be sensitive |
| 60 | +- Keep dependencies up to date (Dependabot is enabled on this repository) |
| 61 | + |
| 62 | +## Disclosure Policy |
| 63 | + |
| 64 | +We follow a coordinated disclosure process. We ask that you: |
| 65 | + |
| 66 | +- Give us reasonable time to fix the vulnerability before public disclosure |
| 67 | +- Do not exploit the vulnerability beyond what is necessary to demonstrate it |
| 68 | +- Do not access or modify data that does not belong to you |
0 commit comments