Storebrand Vulnerability Disclosure Program

Description

The Storebrand Vulnerability Disclosure Program (VDP) provides a clear and secure way for security researchers, customers, and partners to report potential security vulnerabilities affecting Storebrand's digital services and systems.

We encourage responsible, good-faith security research and are committed to working collaboratively with reporters to validate, triage, and remediate legitimate findings. This program outlines which assets are in scope, how vulnerabilities should be reported, and what reporters can expect from Storebrand in terms of response and handling.

Storebrand is committed to coordinated vulnerability disclosure and to protecting customer data, financial information, and service availability. Reports submitted through this program will be handled confidentially and in accordance with applicable laws, regulations, and our internal security and compliance processes.

Bounties

This is a responsible disclosure program without bounties.

Rules of Engagement

Requirements:

• @intigriti.me Required
• User agent: Not applicable
• Automated tooling: max. 5 requests/sec
• Request header: X-Intigriti: f507303e-cba0-429c-ad5b-0c32dc83b9bf-{Username}

By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation Times

Safe harbour for researchers is applied.

In-Scope Assets

The following assets are currently in scope:

• Customer-facing web applications and digital services owned and operated by Storebrand
• Publicly accessible APIs owned and operated by Storebrand
• Mobile applications published and maintained by Storebrand
• Internet-facing systems and services that are part of Storebrand's production environment

Scope List:

Storebrand Asset Management:

• *.sppfonder.se
• *.storebrandrealestate.se
• *.storebrandfunds.com
• *.storebrandfondene.dk
• *.aipmanagement.dk
• *.storebrandam.com

Capital Investment:

• *.capitalinvestment.dk
• *.capitalbolig.dk

Delphi:

• *.storebrandfonder.se
• *.delphifunds.com
• *.delphifonder.se
• *.storebrandfastigheter.se
• *.delphi

Cubera:

• *.cubera.no
• *.cubera.se

SKAGEN Fondene:

• *.skagenfunds.it
• *.skagenfunds.ch
• *.skagenfunds.be
• *.skagenfunds.at
• *.skagenfunds.fr
• *.skagenfunds.de
• *.skagenfunds.ie
• *.skagenfunds.co.uk
• *.skagenfunds.lu
• *.skagenfunds.nl
• *.skagenfunds.is
• *.skagenfunds.fi
• *.skagenfondene.dk
• *.skagenfonder.se
• *.skagenfunds.com
• *.skagenfondene.no
• *.sppkonsult.se
• *.storebrand.dk
• *.storebrand.se
• *.storebrand.com
• *.storebrand.no
• *.kron.no
• *.spp.se

Only assets owned and operated by Storebrand are in scope unless explicitly stated otherwise. If you are unsure whether a specific asset or system is in scope, please use the feedback form to confirm before testing.

Useful Infrastructure Information:

• Production systems are monitored and logged
• Testing must be performed in a non-disruptive manner
• Automated scanning should be limited and respectful
• Please avoid actions that could impact service availability or customer data

If you are unsure whether a specific test is permitted, please contact us before proceeding.

Out of Scope

Important OOS reminder:

Only assets owned and operated by Storebrand are in scope unless explicitly stated otherwise. If you are unsure whether a specific asset or system is in scope, please use the feedback form to confirm before testing.

Out of Scope Categories:

• Third-party services or platforms not owned or operated by Storebrand
• Physical security
• Social engineering (phishing, vishing, smishing)
• Denial-of-Service (DoS / DDoS) attacks
• Issues requiring access to stolen credentials

Application-Level:

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits of rate-limits
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Content injection without being able to modify the HTML
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks aren't sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

General:

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Mobile:

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

Severity Assessment

This program follows Intigriti's triage standards based on the proof of concept.

FAQ

Where can we get credentials?

We currently don't offer any credentials.