Saxo Group Vulnerability Disclosure Policy
We take the security of our systems and services seriously, and we value the global security community. Responsible disclosure of security vulnerabilities helps us ensure the security and privacy of our customers, partners and employees.
If you follow these guidelines when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research
- Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission)
- Recognize your contribution, if you are the first to report the issue and we make a code or configuration change based on the issue
We require that all researchers:
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security analysis
- Perform analysis only within the scope set out below
- Use exploits only to the extent necessary to confirm the presence of a vulnerability and once established, do not abuse the vulnerability further
- Do not exfiltrate data, establish command line access and/or persistence, or pivot to other systems
- Use the defined communication channels (as identified below) to report vulnerability information to us
- Keep information about any suspected or confirmed security issues you’ve discovered confidential between yourself and Saxo Bank until we’ve had 90 days to resolve the issue
- Simulation SaxoInvestor
- Simulation SaxoTraderPRO
- Simulation SaxoTraderGO
- Simulation SaxoOpenAPI, directly or through www.developer.saxo
Out of Scope
Any services hosted by 3rd party providers and services are excluded from scope. These services include:
- News feeds
- Price feeds
In the interest of the safety of our users, staff, the Internet at large, and you as a security researcher, the following test types are excluded from scope:
- Findings from physical testing such as office access (e.g. open doors, tailgating)
- Findings derived primarily from social engineering (e.g. phishing, vishing)
- Findings from applications or systems not listed in the ‘Scope’ section
- UI and UX bugs and spelling mistakes
- Network level Denial of Service (DoS/DDoS) vulnerabilities
- Missing cookie flags and security headers
- Form spamming
Information we do not want to receive:
- Personally identifiable information (PII)
- Financial data (such as credit card or bank account numbers)
- Results from automated scanning tools
Reporting security vulnerabilities
If you believe you’ve found a security issue in one of our products or platforms please send it to us by emailing firstname.lastname@example.org. Please include the following details with your report:
- Description of the location and potential impact of the identified issue(s);
- A detailed description of the steps required to reproduce your findings (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
- Your name/handle and a link for recognition in our Hall of Fame.
If you wish to encrypt the information, you can use our PGP key. See our security.txt for further details.
We aim to patch vulnerabilities within 90 days or less. However, public disclosure of such vulnerabilities before the issue has been corrected will increase risk rather than reduce it, and in order to protect our clients, we request that you do not post or share any information about a potential vulnerability in public until we have investigated, responded to and patched the reported vulnerability and informed our clients (where applicable).
Where applicable, we will coordinate notification of a validated vulnerability with you and would prefer that our respective disclosures be posted simultaneously.