Skip to main content

Security report for fabasoft.com

Fabasoft AG · Technology · Austria

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

43/100

Risk levelHigh

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

Fabasoft AG is an established enterprise technology company specializing in digital business process design and cloud-native solutions, integrating AI to enhance enterprise content management, records management, and business process automation. The company targets organizations undergoing digital transformation, including government and energy sectors, and maintains a strong market position supported by certifications and notable customers. Technically, the website is built on Drupal 10 with modern front-end frameworks and uses Piwik PRO for analytics, demonstrating a mature digital infrastructure. However, a critical security weakness is the lack of a valid SSL certificate and proper HTTPS configuration, which undermines the security posture despite the presence of security headers. Privacy and cookie policies are comprehensive and GDPR compliant, reflecting good privacy practices. Overall, the website is professional and trustworthy but requires urgent remediation of SSL/TLS issues to ensure secure user interactions.

Scanned

This is an earlier scan of fabasoft.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
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

7 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

    • 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

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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

      • 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 fabasoft.com

This scan found 16 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
55
Email security
50
DNS health
50
Network security
100
GDPR outside view
0
Average
43

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

Fabasoft operates a SaaS and cloud platform business model with a focus on AI-enhanced digital ecosystems (Fabasphere) and cloud services. Their offerings include specialized solutions for business and government sectors, such as document and contract management, meeting management, and regulatory compliance tools. The company leverages a strong partnership ecosystem and maintains a consistent brand presence with high-profile clients. Growth indicators include continuous innovation in AI and cloud-native technologies. The company’s nearly 40-year history and enterprise size position it as a mature player in the technology sector.

Security posture

The current security maturity level is moderate due to the presence of security headers and privacy compliance but critically impacted by the absence of a valid SSL certificate and disabled TLS protocols. This exposes users to potential data interception and undermines trust. No public vulnerability disclosure or incident response information is available, which may limit transparency. The company demonstrates awareness of security best practices but must prioritize SSL/TLS remediation and consider publishing incident response contacts to enhance security culture and readiness.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and OCSP stapling to improve security and performance.
  3. Publish a vulnerability disclosure policy or security.txt file to improve transparency and trust.
  4. Provide clear incident response contact information, including security or abuse email addresses.
  5. Enhance contact information availability on the website to improve user trust and support.
Technical notes

Notes

The website uses a modern technology stack centered on Drupal 10 CMS, Bootstrap for responsive design, and FontAwesome for icons, complemented by Lottie animations for enhanced user experience. Analytics are handled via Piwik PRO, indicating a focus on privacy-conscious tracking. The site is mobile-optimized and accessible with good SEO practices. However, the lack of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risk. Performance data is unavailable, but the use of chunked transfer encoding and modern front-end assets suggests moderate performance. Technical risks include potential exposure to man-in-the-middle attacks and user trust degradation due to insecure connections.
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. 77/100Low24 findingsView report
Reviews of this site

Share your experience with fabasoft.com. 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 fabasoft.com.

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.