Security is core to our values, and we value the input of hackers acting in good faith to help us maintain a high standard for the security and privacy for our users. This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good-faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.
When working with us according to this policy, you can expect us to:
- Work with you to understand and validate your report, including a timely initial response to the submission.
- Work to remediate discovered vulnerabilities in a timely manner.
- Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change.
Any service on our domains *.nrk.no, *.nrkbeta.no, *.nrksuper.no and *.p3.no, but not services that are hosted by third parties. Examples of 3rd party services may include, but are not limited to, Akamai, Azure and GCloud. If you have any questions about scope, please contact us on firstname.lastname@example.org.
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.
The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions.
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions, e.g.: login/logout/search.
- Attacks requiring MITM or physical access to a user’s device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.
- Rate limiting or bruteforce issues on non-authentication endpoints.
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies that are not sensitive (e.g. missing flags on authentication cookies are in scope).
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.).
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version].
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
- Open redirect – unless an additional security impact can be demonstrated
Issues that require unlikely user interaction.
We do not offer money or swag as rewards, but we will give you a place in our Security Hall of Fame
How to contact us
Our official communication channel is via email to it-sikkerhetsgruppe
PGP public key: https://keys.openpgp.org/search?q=85EF44309CC0DFC4F7E04393E7BCE5AA9411C063
Fingerprint: 85EF 4430 9CC0 DFC4 F7E0 4393 E7BC E5AA 9411 C063
To encourage vulnerability research and to avoid any confusion between legitimate research and malicious attack, we ask that you attempt, in good faith, to:
- Play by the rules. This includes following this policy any other relevant agreements.
- Report any vulnerability you’ve discovered promptly.
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience.
- Use only the official channels to discuss vulnerability information with us.
- Handle the confidentiality of details of any discovered vulnerabilities according to our Disclosure Policy.
- Perform testing only on in-scope systems, and respect systems and activities which are out-of-scope.
- If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information.
- You should only interact with test accounts you own or with explicit permission from the account holder.
- Do not engage in extortion.
When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:
- Authorized in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy.
- Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls.
- Exempt from restrictions in our Acceptable Usage Policy that would interfere with conducting security research, and we waive those restrictions on a limited basis.
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.
If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our official channels before going any further.
|2020||Sumit Grover (@sumgr0)|
|2020||Aishwarya Kendle (Linkedin)|
|2020||Prateek Thakare (LinkedIn)|
|2020||Husain Murabbi (Hackerone)|
|2020||Mansoor Rangwala (Hackerone)|
|2020||GwanYeong Kim (@sec_karas)|
|2020||Tharun Sai (Linkedin)|
|2021||Ankit Rathore (Linkedin)|
|2021||Naveen Kumawat (Linkedin)|
|2021||Simranjit Singh (Linkedin)|
|2022||Simranjit Singh (Linkedin)|
|2022||Simen Abrahamsen (Linkedin)|
|2022||Ahmad Rahman (Linkedin)|
|2022||Deepanshu Rawat (Linkedin)|
|2022||Simen Abrahamsen (Linkedin)|
|2022||Dipendranath Tarafder (Twitter)|
|2022||Shreyas Koli (Twitter)|
|2023||Martin Ingesen (Linkedin)|