Security report for tatrabanka.sk
Tatra banka, a.s. · Finance · Slovakia
High risk. 20 critical or high findings in GDPR outside view, Network security and 2 other checks.
Tatra banka, a.s. is a leading Slovak financial institution specializing in personal banking services including accounts, loans, payment cards, savings, investments, and insurance. The website reflects a mature digital presence with a strong emphasis on innovation and customer-centric services. It targets Slovak personal banking customers with a comprehensive product portfolio and digital banking capabilities. The bank is part of the Raiffeisen Bank International group, indicating a strong market position and backing. The technical infrastructure is modern, leveraging popular JavaScript libraries, Bootstrap framework, and advanced marketing and analytics tools such as Google Tag Manager and Exponea. The site is mobile optimized and uses secure HTTPS connections with CSRF protections and reCAPTCHA on forms, demonstrating a good security posture. However, explicit security policies and incident response information are not publicly detailed. Overall, the website is professional, trustworthy, and compliant with GDPR and cookie regulations. It integrates multiple contact channels and social media platforms, enhancing customer engagement. No critical vulnerabilities or suspicious patterns were detected, making it a low-risk digital asset for the bank.
Scanned
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
20 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
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
- 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: Google Analytics, Facebook, LinkedIn, YouTube
What to do: Document all third-party data sharing in your privacy policy
- Critical
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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
Need hands-on remediation? Email guard@offseq.com
Keep watching tatrabanka.sk
This scan found 29 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. See sample alerts.
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
- 82
- Security headers
- 80
- Email security
- 67
- DNS health
- 90
- Network security
- 0
- GDPR outside view
- 25
- Average
- 57
- 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
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Publish a dedicated security policy and incident response information page to improve transparency and trust.
- Implement and publish a security.txt file to facilitate responsible vulnerability disclosure.
- Enhance website accessibility to meet higher standards for users with disabilities.
- Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
- Improve cookie consent mechanisms to provide clearer user choices and compliance documentation.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Tatra banka, a.s.
- Description
- Tatra banka ponúka komplexnú ponuku bankových služieb a osobný prístup ku klientom. Sme lídrom v inováciách, ktoré menia váš svet. Každý deň.
- Key services
- Personal accounts and payments, Loans (mortgage, consumer, refinancing), Payment cards (credit, debit), Savings, investments, and pension products, Insurance products, Digital banking services and mobile apps
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- jQuery, Bootstrap, jQuery UI, Moment.js, Slick Carousel, Google Tag Manager, Nuance Chatbot, Exponea Marketing SDK, Luigisbox Autocomplete
- Frameworks
- Bootstrap
- Platforms
- Web
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- CSRF token implemented
- No exposed sensitive data in HTML
- Use of reCAPTCHA for forms
- No obvious vulnerable libraries detected
Analytics and tracking
- Services
- Google Tag Manager, Exponea
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Tracking pixels
- Exponea
- Marketing tools
- Exponea Marketing SDK, Luigisbox Autocomplete
- Transparency
- good
Site quality
- Design
- excellent
- User experience
- good
- Content relevance
- excellent
- Navigation
- good
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is professionally designed and well maintained.
- Strong focus on personal banking products and services.
- Comprehensive legal and privacy documentation available.
- Multiple contact channels including phone and forms.
- Use of modern web technologies and marketing tools.
- No signs of malicious or suspicious content.
- Good integration of social media and external trusted domains.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- 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
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- 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
- 37/100High34 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.
Reviews of this site
Share your experience with tatrabanka.sk. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review tatrabanka.sk.