Security report for bouvet.no

Name: Dark-web exposure summary for bouvet.no
Creator: OffSeq Breach

Bouvet ASA · Technology · Norway

High risk. 19 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

0–100, higher is better. How it is calculated

Bouvet ASA is a leading Norwegian-owned consulting company specializing in IT, advisory, design, and digital communication services. The company serves a broad range of private and public sector clients, positioning itself as a key digital transformation partner in the Nordic region. Their service portfolio includes designing, developing, managing, and advising on IT solutions and digital communication strategies. The website reflects a mature digital presence with professional design, clear navigation, and comprehensive content tailored to their target audience of businesses and societal actors across industries. Technically, the website leverages modern web technologies including Enonic XP CMS, Google Fonts, Matomo analytics for privacy-conscious tracking, and Cloudflare for performance and security enhancements. The site is well-optimized for mobile devices, accessible, and SEO-friendly. Security best practices are observed with HTTPS enforcement, cookie consent mechanisms, and published information security policies. However, explicit security headers and vulnerability disclosure mechanisms could be improved. From a security posture perspective, Bouvet demonstrates a strong commitment to information security, evidenced by ISO 27001 certification and published security guidelines. The presence of a security incident reporting page indicates readiness for incident response. No critical vulnerabilities or security issues were detected in the website content or configuration. Privacy compliance is robust with clear cookie policies and GDPR-aligned disclosures. Overall, Bouvet ASA's website and digital infrastructure reflect a reputable, secure, and professionally managed business entity with a strong market position in IT consulting. The lack of publicly available WHOIS data is consistent with Norwegian domain privacy norms and does not detract from the company's legitimacy. Strategic recommendations include enhancing transparency on security headers, adding a public vulnerability disclosure policy, and providing direct security contact information to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view: 35/ 100 · High
Checks completed: 7of 7

NIS2 Art. 21(2)

(a) Risk analysis and security policies: Not visible from outside
(b) Incident handling: One indicator
(c) Business continuity, backups and crisis management: Not visible from outside
(d) Supply chain security: Not visible from outside
(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
(f) Assessing the effectiveness of security measures: Not visible from outside
(g) Cyber hygiene and security training: Not visible from outside
(h) Cryptography and encryption: Partly checked
(i) HR security, access control and asset management: One indicator
(j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

19 findings rated critical or high. Fix these first.

Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- Critical
  Critical Service Exposed: Telnet
  Port 23 (Telnet) is publicly accessible - Telnet - Unencrypted remote access
  What to do: Immediately restrict access to Telnet using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: SMB
  Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk
  What to do: Immediately restrict access to SMB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MSSQL
  Port 1433 (MSSQL) is publicly accessible - MSSQL - Database server
  What to do: Immediately restrict access to MSSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Oracle
  Port 1521 (Oracle) is publicly accessible - Oracle - Database server
  What to do: Immediately restrict access to Oracle using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MySQL
  Port 3306 (MySQL) is publicly accessible - MySQL - Database server
  What to do: Immediately restrict access to MySQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: RDP
  Port 3389 (RDP) is publicly accessible - RDP - Remote Desktop, prime ransomware target
  What to do: Immediately restrict access to RDP using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: PostgreSQL
  Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server
  What to do: Immediately restrict access to PostgreSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Redis
  Port 6379 (Redis) is publicly accessible - Redis - In-memory database
  What to do: Immediately restrict access to Redis using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MongoDB
  Port 27017 (MongoDB) is publicly accessible - MongoDB - NoSQL database
  What to do: Immediately restrict access to MongoDB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: FTP
  Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
  What to do: Consider restricting access to FTP or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: RPC
  Port 135 (RPC) is publicly accessible - RPC - Windows RPC endpoint
  What to do: Consider restricting access to RPC or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: NetBIOS
  Port 139 (NetBIOS) is publicly accessible - NetBIOS - Windows file sharing
  What to do: Consider restricting access to NetBIOS or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: Elasticsearch
  Port 9200 (Elasticsearch) is publicly accessible - Elasticsearch - Search engine
  What to do: Consider restricting access to Elasticsearch or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
Security headers
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
- High
  Missing Strict-Transport-Security header
  Forces HTTPS connections
  What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"
  References
  - CWE-319
  - OWASP A04:2025
  - ASVS V3.4.1
  - RFC 6797 §6.1.1
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
  - NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- High
  No Privacy Policy found
  GDPR requires a clear and accessible privacy policy
  What to do: Add a comprehensive privacy policy page and link to it prominently
  References
  - GDPR Art. 12
  - GDPR Art. 13
  - NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- High
  No Cookie Policy found
  GDPR requires clear information about cookie usage
  What to do: Add a dedicated cookie policy explaining cookie usage and purposes
  References
  - ePrivacy Art. 5(3)
- High
  No Cookie Consent Banner found
  GDPR requires explicit consent for non-essential cookies
  What to do: Implement a cookie consent banner that appears on first visit
  References
  - GDPR Art. 7
  - ePrivacy Art. 5(3)
  - NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
  Third-party services without privacy policy
  Detected services: Facebook, LinkedIn, YouTube, Google APIs
  What to do: Document all third-party data sharing in your privacy policy
  References
  - GDPR Art. 13(1)(e)
SSL/TLS
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
- High
  Weak SSL Key Length
  SSL certificate uses 256-bit key, which is considered weak
  What to do: Use at least 2048-bit RSA or 256-bit ECC key
  References
  - CWE-326
  - OWASP A04:2025
  - Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
  - NIST SC-13: NIST SP 800-53 Rev. 5 SC-13: Cryptographic Protection

Need hands-on remediation? Email guard@offseq.com

Keep watching bouvet.no

This scan found 30 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

TLS certificates and expiry
DNS records
SPF, DKIM and DMARC
Security headers
GDPR and NIS2 posture
Exposed services
Third-party trackers
Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

The complete analysis as a PDF you can cite
Email delivery with an unlock code
Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS: 75
Security headers: 60
Email security: 85
DNS health: 90
Network security: 0
GDPR outside view: 35
Average: 58
After the cap: 49

Not counted

NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

The certificate is not trusted by browsers
The website is not served over HTTPS
A database, remote desktop, file-sharing or Telnet service is reachable from the internet · found on this site
The page loads a script from a compromised source
The domain registration has expired
SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

Critical0–25
High26–49
Medium50–75
Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention bouvet.no, from OffSeq Breach.

Total records: 17
Employees: 1
Customers: 8
Third parties: 8
Weak passwords: 6%

Latest record dated 2025-07-01 · 5 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for bouvet.no.

Select it in the checkout above.

Masked preview

–fs.bouvet.no2025-07-01

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach Monitor on Breach

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Bouvet ASA operates as a large, established IT consulting firm with a strong foothold in the Nordic market. Their competitive advantage lies in their broad expertise across IT, design, and communication, combined with close customer relationships and a reputation for quality. The business model focuses on delivering consulting services and digital solutions to both private and public sectors, including energy, transportation, and government entities. Revenue streams likely include project-based consulting, managed services, and training courses. The company maintains a partnership ecosystem with regional sites in Sweden and English language offerings, supporting international reach. Growth indicators include active content sharing via blogs, podcasts, and reports, as well as frequent training seminars. The company’s transparent communication of certifications, ethical guidelines, and security policies enhances its market credibility and client trust.

Security posture

Bouvet ASA exhibits a mature security posture with ISO 27001 certification and published information security policies. The website enforces HTTPS and employs cookie consent mechanisms aligned with GDPR requirements. Security incident reporting channels are available, indicating preparedness for incident management. The use of privacy-respecting analytics (Matomo) and absence of exposed sensitive data further strengthen their security stance. However, the website could improve by explicitly publishing security headers such as Content-Security-Policy and providing a dedicated vulnerability disclosure policy or security.txt file. No critical vulnerabilities or security misconfigurations were detected. Overall, the security culture appears strong, supporting business continuity and regulatory compliance.

Recommendations

Publish detailed security headers (CSP, X-Frame-Options, X-Content-Type-Options) explicitly on the website.
Implement and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Provide direct security contact emails (e.g., security@bouvet.no) to facilitate incident reporting and communication.
Enhance transparency on data retention policies related to analytics and user data.
Continue regular security audits and update privacy policies to maintain GDPR and NIS2 compliance.

Contact details published on the site

Legal name: Bouvet ASA
Registration number: 974 442 167

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: Bouvet ASA
Description: Bouvet er et norskeid, ledende konsulentselskap innen IT, rådgivning, design og kommunikasjon. Vår årelange erfaring, nærhet til kundene og brede kompetanse gjør oss til en svært ettertraktet digitaliseringspartner for både private og offentlige aktører.
Key services: IT-løsninger design, utvikling, forvaltning, rådgivning, digital kommunikasjon
Content quality: excellent
Branding: consistent

Technology

Stack: Google Fonts (Inter), Matomo Analytics, Cloudflare Insights, YouTube iframe API
Platforms: Enonic XP CMS
Performance: fast
Mobile: excellent
Accessibility: good
SEO: good

Security

Observed score

85/100

Good practices seen

HTTPS enforced
Cookie consent banner with categories
Security incident reporting link
Information security guidelines published

Analytics and tracking

Services: Matomo, Google Tag Manager, Cloudflare Insights
Tracking level: moderate
Privacy practices: good

Advertising

Tracking pixels: Facebook Pixel, LinkedIn Insight, Matomo
Marketing tools: Matomo Analytics, Cloudflare Insights
Transparency: good

Site quality

Design: excellent
User experience: excellent
Content relevance: excellent
Navigation: excellent
Professionalism: excellent
Trustworthiness: high

Key observations

Website is fully accessible with rich content and professional design.
Strong focus on IT consulting, digital transformation, and communication services.
Comprehensive cookie consent and privacy policy in Norwegian language.
No direct contact emails or phone numbers explicitly listed; contact via forms and office locations.
Use of modern web technologies and analytics tools with privacy considerations.
No signs of security blocking or WAF challenges.
WHOIS data is privacy protected as per Norid policies for .no domains.

Technical notes

Notes

The website is built on a modern technology stack featuring Enonic XP CMS, Google Fonts, and Matomo analytics, hosted behind Cloudflare for performance and security. The site is well-optimized for mobile devices and accessibility, with fast loading times and proper SEO meta tags. JavaScript libraries include YouTube iframe API for embedded videos and Matomo scripts for analytics. Cookie consent is implemented with granular categories for necessary, marketing, and statistics cookies. The technical infrastructure supports a professional and scalable digital presence with minimal technical debt. Opportunities exist to enhance security header implementation and formalize vulnerability disclosure processes to reduce technical risks.

Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)

Retrieved 2026-10-25

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Priority findings

Network security

Critical Service Exposed: Telnet

Critical Service Exposed: SMB

Critical Service Exposed: MSSQL

Critical Service Exposed: Oracle

Critical Service Exposed: MySQL

Critical Service Exposed: RDP

Critical Service Exposed: PostgreSQL

Critical Service Exposed: Redis

Critical Service Exposed: MongoDB

High-Risk Service Exposed: FTP

High-Risk Service Exposed: RPC

High-Risk Service Exposed: NetBIOS

High-Risk Service Exposed: Elasticsearch

Security headers

Missing Strict-Transport-Security header

GDPR outside view

No Privacy Policy found

No Cookie Policy found

No Cookie Consent Banner found

Third-party services without privacy policy

SSL/TLS

Weak SSL Key Length

Keep watching bouvet.no

Daily monitoring

Full report

Results by check

Security headers, 5 findings, score 60/100

SSL/TLS, 3 findings, score 75/100

Email security, 3 findings, score 85/100

DNS health, 1 finding, score 90/100

Network security, 14 findings, score 0/100

GDPR outside view, 4 findings, score 35/100

NIS2 outside view, Earlier method, rescan for details · not counted in the security score–