Storebrand Responsible Disclosure
By Storebrand Vulnerability disclosure program on Intigriti storebrand.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 40
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 3 days
| Exceptional | 3 Working days |
- Safe harbor
-
Partial
We encourage responsible, good-faith security research and are committed to working collaboratively with reporters to validate, triage, and remediate legitimate findings.
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
40 assets you may test, 3 excluded.
Wildcard domains 38
- *.aipmanagement.dk
- *.capitalbolig.dk
- *.capitalinvestment.dk
- *.cubera.no
- *.cubera.se
- *.delphifonder.se
- *.delphifunds.com
- *.kniftrygghet.no
- *.kron.no
- *.skagenfondene.dk
- *.skagenfondene.no
- *.skagenfonder.se
- *.skagenfunds.at
- *.skagenfunds.be
- *.skagenfunds.ch
- *.skagenfunds.com
- *.skagenfunds.co.uk
- *.skagenfunds.de
- *.skagenfunds.fi
- *.skagenfunds.fr
- *.skagenfunds.ie
- *.skagenfunds.is
- *.skagenfunds.it
- *.skagenfunds.lu
- *.skagenfunds.nl
- *.sppfonder.se
- *.sppkonsult.se
- *.spp.se
- *.storebrandam.com
- *.storebrand.com
- *.storebrand.dk
- *.storebrandfastigheter.se
- *.storebrandfondene.dk
- *.storebrandfonder.se
- *.storebrandfunds.com
- *.storebrand.no
- *.storebrandrealestate.se
- *.storebrand.se
Android apps 1
- Kron - Sparing og pensjon - Android No bounty
iOS apps 1
- Kron - Sparing og pensjon - iOS No bounty
Out of scope (3)
- f29baf0e-81df-4090-a5a5-f33cb9566b0d.storebrand.no
- kvadrat.no
- viavika.no
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Storebrand Responsible Disclosure (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Respect the scope of the program
-
Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)
-
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.
Not accepted
-
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
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 11 minutes ago.
-
Scope +
Added to scope: Kron - Sparing og pensjon - Android
-
Scope +
Added to scope: Kron - Sparing og pensjon - iOS
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
*.delphi
-
Scope added
*.kniftrygghet.no
-
Scope removed
kvadrat.no (out of scope)
-
Scope removed
*.delphi
-
Scope removed
viavika.no (out of scope)
-
Scope removed
*.storebrandfunds.com
-
Scope removed
*.storebrandrealestate.se
-
Scope removed
*.skagenfunds.it
-
Scope removed
*.storebrandfondene.dk
-
Scope removed
*.sppfonder.se
-
Scope removed
*.storebrand.dk
-
Scope removed
*.delphifunds.com
-
Scope removed
*.skagenfunds.ch
-
Scope removed
*.skagenfunds.be
-
Scope removed
*.sppkonsult.se
-
Scope removed
*.delphifonder.se
-
Scope removed
*.skagenfunds.at
-
Scope removed
*.storebrand.se
-
Scope removed
*.cubera.se
-
Scope removed
*.storebrand.com
-
Scope removed
*.capitalbolig.dk
-
Scope removed
*.storebrandam.com
-
Scope removed
*.storebrandfastigheter.se
-
Scope removed
*.skagenfunds.com
-
Scope removed
*.skagenfunds.is
-
Scope removed
*.aipmanagement.dk
-
Scope removed
*.spp.se
-
Scope removed
*.skagenfunds.fi
-
Scope removed
*.skagenfondene.no
-
Scope removed
*.skagenfunds.fr
-
Scope removed
*.kron.no
-
Scope removed
*.skagenfunds.de
-
Scope removed
*.skagenfunds.ie
-
Scope removed
*.cubera.no
-
Scope removed
*.skagenfonder.se
-
Scope removed
*.skagenfunds.lu
-
Scope removed
*.storebrand.no
-
Scope removed
*.skagenfunds.nl
-
Scope removed
*.skagenfondene.dk
-
Scope removed
*.capitalinvestment.dk
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
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.
Rules of engagement
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
We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
| Vulnerability Severity | Time to validate |
|---|---|
| Exceptional | 3 Working days |
| Critical | 3 Working days |
| High | 5 Working days |
| Medium | 10 Working days |
| Low | 10 Working days |
In scope
Introduction
We are pleased to launch Storebrand’s Vulnerability Disclosure Program. While we continuously work to improve the security of our systems, we recognize that vulnerabilities can still occur. We welcome responsible, good-faith security research and appreciate your help in identifying issues we may have missed.
This section outlines which assets are in scope, what types of findings are most valuable to us, and any relevant technical context to support your research.
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
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.
Codex
- Storebrand-BBP-Authorization: v1
- Challenge: codex-7b43b06f-3f64-4bd1-92f0-560a05e486c1
- Program: Storebrand Responsible Disclosure
- Campaign-ID: SPP-CODEX-2026-001
- Scope: all sites in this page
- Authorization: all activities are allowed except those explicitly defined as restricted.
- Restrictions: no denial of service, customer-data access, destructive actions, or third-party testing
- Issued-At: 2026-11-02T10:00:00Z
- Expires-At: 2026-11-09T10:00:00Z
- Authorized-By: Storebrand Responsible Disclosure Program Owner
Feedback
If you would like to help us improve this program or share feedback, please submit anonymous feedback here:
Please note this form will be checked periodically and should not be used for submission or support queries.
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.
- 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
- 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
- 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
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.