Skip to main content

Security report for fara.no

FARA · Transportation · Norway

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

71/100

Risk levelMedium

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

FARA is a Norwegian-based technology company specializing in public transport solutions, including ticketing systems, passenger information, and real-time monitoring. Established in 2005, the company offers a comprehensive suite of products targeting passengers, operators, and public transport authorities. Their market position is that of an established player in the Nordic and European transportation technology sector, with a medium-sized business profile and a clear B2B focus. The website reflects a professional and consistent brand image with good content quality and clear navigation tailored to their target audience. Technically, the website is built on WordPress with modern integrations such as Google Analytics, Google Tag Manager, Cookiebot for consent management, and HubSpot for marketing automation. The site is mobile-optimized and SEO-friendly, though accessibility features are basic. Performance is moderate, with room for improvement in hosting transparency and technical optimizations. From a security perspective, the site enforces HTTPS and uses cookie consent mechanisms, but lacks visible security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy compliance is strong with clear privacy and cookie policies and GDPR indicators. Business credibility is supported by trust signals such as client logos, social media presence, and comprehensive legal documents. Overall, the website presents a low-risk profile with a solid security posture and good privacy compliance. Strategic recommendations include enhancing security headers, publishing a security policy and incident response contacts, and improving accessibility compliance to further strengthen trust and security culture.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (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

5 findings rated critical or high. Fix these first.

  1. 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"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

      • 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';…

  2. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • 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

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching fara.no

This scan found 21 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
57
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
83
Average
71

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
  • 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

FARA operates in the transportation technology sector, providing advanced ticketing and passenger information solutions. Their competitive advantage lies in a broad product portfolio including account-based ticketing, contactless EMV ticketing, and real-time information systems. The business model is B2B, serving public transport authorities and operators primarily in Nordic and European markets. Revenue streams likely include software licensing, service contracts, and support. The company demonstrates growth through partnerships and client logos displayed on the site. Their digital presence is supported by integrations with marketing and analytics platforms, indicating a mature marketing strategy. Strategic observations suggest a focus on innovation in contactless and real-time technologies, positioning them well for future market demands.

Security posture

The security maturity level of the website is moderate to good. HTTPS is enforced, and cookie consent is managed via Cookiebot, indicating GDPR awareness. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options is a gap that could expose the site to certain web-based attacks. No incident response or security policy information is published, which limits transparency and preparedness perception. No vulnerabilities or exposed sensitive data were found in the HTML content. The use of third-party scripts is extensive but managed with consent. Compliance with GDPR is evident, but NIS2 or other frameworks are not explicitly referenced. Overall, the security culture appears adequate but could benefit from formalized policies and enhanced technical controls.

Recommendations

  1. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish a dedicated security policy page and provide clear incident response contact channels such as security@ or abuse@ email addresses.
  3. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  4. Enhance website accessibility features to meet recognized standards and improve user inclusivity.
  5. Conduct regular audits of third-party scripts and dependencies to identify and remediate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
FARA
Description
Making travel easy - for passengers, operators and public transport authorities
Key services
Account Based Ticketing (ABT), Contactless EMV Ticketing, Customer Service Applications, Driver Ticketing Applications, Passenger Information Systems, Real Time Information and Monitoring, Automatic Passenger Counting, Traffic Light Priority, Driver Communication Tools
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Analytics, Google Tag Manager, Cookiebot, HubSpot, Google Maps API
Frameworks
Yoast SEO
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Analytics with consent

Analytics and tracking

Services
Google Analytics, HubSpot, Jetpack Stats
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Cookiebot, HubSpot, Jetpack Stats
Marketing tools
HubSpot
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well-structured
  2. Comprehensive product and service offerings in public transport technology
  3. Strong presence of privacy and cookie policies with consent management
  4. No direct company emails or phone numbers found on the homepage or footer
  5. Social media links are consistent with company branding
  6. Use of multiple third-party analytics and marketing tools with consent
  7. No visible security policy or incident response contacts
  8. No security.txt or vulnerability disclosure found
Technical notes

Notes

The website is built on WordPress CMS with a modern tech stack including jQuery, Google Analytics, Google Tag Manager, Cookiebot, and HubSpot marketing tools. SEO is managed via Yoast SEO plugin, contributing to good meta tag and structured data implementation. Performance is moderate, with caching and optimization plugins indicated by CSS cache files. Mobile optimization is good, and the site uses responsive design principles. However, hosting provider details are not explicit, which could be a point for further investigation. The technical debt appears low, but improvements in security headers and accessibility compliance are recommended to reduce operational 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.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 75/100Medium15 findings · partial scanView report
Reviews of this site

Share your experience with fara.no. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review fara.no.

Feedback on this report

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

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.