Security report for okm.fi

Opetus- ja kulttuuriministeriö · Government · Finland

High risk. 19 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

40/100

Risk levelHigh

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

Opetus- ja kulttuuriministeriö (OKM) is the Finnish Ministry of Education and Culture responsible for national policies in education, culture, sports, youth work, libraries, and religious affairs. The website serves as an official government portal providing information, news, publications, and resources related to these sectors. The site targets Finnish citizens, educational institutions, cultural organizations, and government stakeholders. It operates under the Finnish government umbrella and maintains a strong authoritative position in its domain. Technically, the website is built on the Liferay CMS platform, utilizing modern JavaScript libraries including React and Alloy UI components. The site demonstrates good mobile optimization, accessibility, and SEO practices. Hosting is managed by the Finnish government IT center Valtori, ensuring reliable infrastructure. From a security perspective, the site enforces HTTPS and includes cookie consent mechanisms aligned with GDPR. While DNSSEC is not implemented, no critical vulnerabilities or exposed sensitive data were detected. Security headers are partially present, and there is room for enhancement by adding additional headers and publishing formal security policies. Overall, the website exhibits a mature digital presence with strong business credibility and good technical implementation. Recommendations include improving DNS security, enhancing HTTP security headers, and publishing security and incident response information to further strengthen trust and compliance.

Scanned

This is an earlier scan of okm.fi. View the latest report

NIS2 and GDPR posture

GDPR outside view: 25/ 100 · Critical
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.

GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
  EU business without adequate privacy measures
  EU businesses are subject to strict GDPR requirements
  What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures
- 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
  Third-party services without privacy policy
  Detected services: Facebook, Twitter, LinkedIn, YouTube
  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.
- Critical
  Unable to retrieve SSL certificate
  Could not establish secure connection to retrieve certificate information
  What to do: Check if the server is accessible and SSL/TLS is properly configured
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 Content-Security-Policy header
  Controls resources the browser is allowed to load
  What to do: Implement a Content-Security-Policy appropriate for your application
  References
  - ASVS V3.4.3
  - OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

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

Keep watching okm.fi

This scan found 31 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: 0
Security headers: 60
Email security: 70
DNS health: 85
Network security: 0
GDPR outside view: 25
Average: 40

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

Technical appendix

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

Business context

Business profile

OKM holds a key government role in Finland, overseeing education and cultural sectors. Its market position is authoritative and non-commercial, focusing on public service delivery. The ministry's business model revolves around policy-making, funding allocation, and public communication. Revenue streams are government-funded. The target audience includes students, educators, cultural institutions, and the general public. The website supports transparency and engagement through news, publications, and social media. Partnerships with other ministries and government agencies are evident through linked domains. The ministry's operations reflect stability and long-term government backing.

Security posture

The website demonstrates a solid security posture with mandatory HTTPS and cookie consent aligned with GDPR. No signs of malware, phishing, or exposed credentials were found. However, the absence of DNSSEC and some recommended security headers (e.g., Content-Security-Policy) indicates areas for improvement. There is no public security policy or incident response contact, which could enhance transparency and preparedness. The current security maturity is good but can be elevated by adopting additional best practices and formal disclosures.

Recommendations

Implement DNSSEC to secure DNS queries and prevent spoofing.
Add comprehensive security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
Publish a formal security policy and incident response contact information on the website.
Develop and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
Continue monitoring and updating third-party libraries to avoid vulnerabilities and maintain compliance.

Contact details published on the site

Addresses

Vapaudenkatu 58, 40100 Jyväskylä, Finland (map, opens in a new tab)

Legal name

Opetus- ja kulttuuriministeriö

Registration number

0245872-8

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: Opetus- ja kulttuuriministeriö
Description: Opetus- ja kulttuuriministeriön vastuulle kuuluvat valtioneuvostossa tiede, koulutus ja varhaiskasvatus; taide, kulttuuri, liikunta ja nuorisotyö; arkisto-, museo- ja yleinen kirjastotoimi; evankelis-luterilainen kirkko, ortodoksinen kirkkokunta sekä muut uskonnolliset yhdyskunnat; opintotuki ja tekijänoikeus.
Key services: Education policy and administration, Cultural affairs, Library and museum oversight, Religious community affairs, Student financial aid, Copyright management
Content quality: good
Branding: consistent

Technology

Stack: JavaScript, jQuery, React, Liferay Portal, AUI (Alloy UI), Clay UI, Metal.js
Frameworks: Liferay
Platforms: Web
Performance: moderate
Mobile: good
Accessibility: good
SEO: good

Security

Observed score

85/100

Good practices seen

HTTPS enforced
No DNSSEC
Cookie consent banner present
No exposed sensitive data detected

Analytics and tracking

Tracking level: minimal
Privacy practices: good

Advertising

Transparency: poor

Site quality

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

Key observations

Official Finnish government ministry website
Content is in Finnish with language alternatives
Comprehensive cookie consent and privacy policy present
No signs of blocking or WAF challenges
Uses modern web technologies and Liferay CMS
Social media presence on major platforms
No exposed sensitive data or security issues detected

Technical notes

Notes

The website is built on a robust Liferay CMS platform with extensive use of JavaScript libraries including React and Alloy UI, indicating a modern and modular front-end architecture. The site loads multiple CSS and JS resources efficiently, though performance is moderate likely due to the complexity and volume of resources. Mobile optimization and accessibility are well addressed, with responsive design and ARIA attributes. SEO is supported by proper meta tags and Open Graph data. Hosting by a government IT center ensures reliability and compliance with government standards. Opportunities exist to optimize performance further and enhance security headers.

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

Earlier scans of this domain

31 Oct 202549/100High41 findingsView report

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

GDPR outside view

EU business without adequate privacy measures

No Privacy Policy found

No Cookie Policy found

Third-party services without privacy policy

SSL/TLS

Unable to retrieve SSL certificate

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 Content-Security-Policy header