Skip to main content

Security report for ombudsstelle-zug.ch

Ombudsstelle Kanton Zug · Government · Switzerland

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

The Ombudsstelle Kanton Zug website serves as the official online presence for the canton Zug's ombudsman office, providing independent, neutral, confidential, and free services to citizens facing conflicts or difficulties with cantonal or municipal authorities. The site targets local residents seeking assistance with administrative disputes and offers key services including mediation, information, and a whistleblowing reporting channel. The website is professionally designed with clear navigation and consistent branding, reflecting its government affiliation and public service mission. Technically, the website employs a simple technology stack primarily based on jQuery and custom JavaScript, with responsive design elements for mobile optimization. While the site performs moderately well and includes essential meta tags, it lacks advanced SEO and accessibility features. No CMS or hosting provider details are evident from the data. The absence of analytics and tracking scripts suggests minimal user tracking, aligning with privacy considerations. From a security perspective, the site appears to use HTTPS (implied by domain), but no explicit security headers or advanced security policies are detected. There are no visible vulnerabilities or exposed sensitive data, but the lack of privacy and cookie policies represents a compliance gap, especially under GDPR. Incident response and vulnerability disclosure mechanisms are not publicly documented, which could be improved to enhance trust and security posture. Overall, the website is trustworthy and professional, serving an essential government function with clear contact information and a transparent mission. However, to strengthen compliance and security, the organization should implement and publish privacy and cookie policies, enforce security headers, and consider formalizing incident response and vulnerability disclosure processes.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

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

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

Keep watching ombudsstelle-zug.ch

This scan found 26 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
62
Security headers
15
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
60

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

The Ombudsstelle Kanton Zug operates as a small, essential government entity focused on providing ombudsman services within the canton of Zug, Switzerland. Its market position is that of an official public service, offering conflict resolution and administrative support to local citizens. The business model is non-profit and service-oriented, relying on government funding and mandates. The target customer segment includes residents and individuals interacting with cantonal and municipal authorities. The organization maintains a partnership ecosystem primarily within government domains, as evidenced by links to zug.ch. Growth indicators are not explicit, but the presence of a whistleblowing channel suggests responsiveness to evolving governance needs. Strategic observations highlight the importance of digital maturity improvements and compliance enhancements to maintain public trust and operational effectiveness.

Security posture

The current security maturity level of the website is moderate. The site uses HTTPS, which is fundamental, but lacks visible security headers such as Content-Security-Policy or X-Frame-Options that help mitigate common web attacks. No vulnerabilities or exposed sensitive data were detected in the provided content. However, the absence of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. Incident response readiness and vulnerability disclosure mechanisms are not publicly available, limiting transparency and preparedness. The security culture appears basic, with minimal tracking and no aggressive data collection, which aligns with the organization's public service nature. Enhancing security policies and publishing clear compliance documentation would improve the overall security posture and stakeholder confidence.

Recommendations

  1. Publish comprehensive privacy and cookie policies to ensure GDPR compliance and transparency.
  2. Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and HSTS to strengthen web security.
  3. Establish and publicly document incident response and vulnerability disclosure procedures to improve security readiness and trust.
  4. Conduct a security audit to identify and remediate any potential vulnerabilities or outdated libraries.
  5. Enhance accessibility and SEO features to improve user experience and discoverability.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ombudsstelle Kanton Zug
Description
Die Ombudsstelle unterstützt die Suche nach Lösungen bei Schwierigkeiten zwischen der Bevölkerung und der Kantonalen Verwaltung Zug
Key services
Mediation and conflict resolution between citizens and cantonal/municipal administration, Information and support regarding administrative decisions, Whistleblowing reporting channel
Content quality
good
Branding
consistent

Technology

Stack
jQuery
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS implied by domain but not confirmed in data
  • No visible forms with password or sensitive input fields on homepage

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is an official government ombudsman service for canton Zug
  2. Content is in German language targeting local citizens
  3. No privacy or cookie policies found, which is a compliance gap
  4. No visible analytics or tracking scripts detected
  5. Simple tech stack with jQuery and custom JS
  6. Contact information is clearly presented with official canton email and phone
  7. No social media links found
  8. No forms on homepage but contact form exists on separate page
  9. No security headers or advanced security policies detected in provided data
Technical notes

Notes

The website is built using a straightforward technology stack centered on jQuery and custom JavaScript files, with CSS for styling and responsive design. The HTML structure is valid and includes essential meta tags for description, language, viewport, and robots directives. No CMS or advanced frameworks are detected, indicating a custom or lightweight platform. Performance is moderate, with no explicit indicators of slow loading but also no advanced optimization techniques evident. Mobile optimization is good, supported by responsive CSS. Accessibility features are basic, with room for improvement. The absence of analytics and tracking scripts suggests minimal data collection, which aligns with privacy considerations but limits marketing insights. Overall, the technical infrastructure is stable but could benefit from modernization and enhanced security configurations.
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

Reviews of this site

Share your experience with ombudsstelle-zug.ch. 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 ombudsstelle-zug.ch.

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.