Skip to main content

Security report for trusted-introducer.org

Task Force CSIRT · Technology · N/a

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

The Task Force CSIRT website serves as a central hub for cybersecurity incident response teams, focusing on fostering a trusted community with a European emphasis. It offers core services including community collaboration, training through TRANSITS, and the Trusted Introducer infrastructure which maintains a directory of cybersecurity teams. The website positions itself as a key player in the cybersecurity incident response ecosystem, targeting professionals and organizations involved in security operations and incident handling. Technically, the website employs modern web technologies such as Bootstrap for responsive design, SVG for graphics, and standard CSS and JavaScript. The site is hosted under a reputable registrar (Gandi SAS) with HTTPS enabled, ensuring secure communications. The site demonstrates good mobile optimization and basic accessibility features, though no CMS or advanced frameworks are detected. From a security perspective, the site benefits from HTTPS and domain transfer protection but lacks DNSSEC and explicit security headers. There is no visible incident response contact or vulnerability disclosure policy, and cookie consent mechanisms are absent, which could be improved for compliance. No analytics or tracking scripts are detected, indicating a privacy-conscious approach. Overall, the website is professional, trustworthy, and focused on its niche audience. It could enhance its security posture and privacy compliance by adding DNSSEC, security headers, cookie consent, and clearer contact and policy disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

4 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 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. GDPR outside view

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

    • 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

    • 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

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

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

Keep watching trusted-introducer.org

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. 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
77
Security headers
65
Email security
70
DNS health
70
Network security
100
GDPR outside view
53
Average
73

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

Task Force CSIRT operates as an essential entity within the cybersecurity sector, providing community-building, training, and trusted infrastructure services. Its market position is strong within the European cybersecurity incident response community, leveraging long domain tenure since 2008. The business model revolves around service provision and community support rather than commercial sales. The absence of direct contact information and limited marketing tools suggests a focus on professional and trusted relationships rather than broad consumer outreach. The partnership ecosystem includes related subdomains for restricted access and self-service portals, indicating a structured service delivery approach.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enabled and domain transfer protection. However, the lack of DNSSEC and security headers such as Content Security Policy or HSTS reduces its defense-in-depth. No exposed sensitive data or vulnerable libraries were detected in the provided content. The absence of explicit incident response contact channels and vulnerability disclosure policies limits transparency and responsiveness. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. Overall, the security maturity is adequate but could be improved with standard best practices and clearer security governance documentation.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options.
  3. Add a cookie policy and consent mechanism to comply fully with GDPR and privacy regulations.
  4. Publish clear incident response contact information and a vulnerability disclosure policy to improve transparency and trust.
  5. Consider adding terms of service and data protection officer contact details to strengthen compliance and governance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Task Force CSIRT
Description
Home for Computer Security Incident Response Teams and all cybersecurity entities — Empowering a global network with European focus through trust, collaboration and progress in cybersecurity.
Key services
TF-CSIRT Community collaboration, TRANSITS training services, Trusted Introducer (TI) infrastructure and directory services
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap (navbar classes), CSS stylesheets, JavaScript, SVG graphics
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on cybersecurity incident response community and services.
  3. No explicit contact emails or phone numbers found on the main page.
  4. Privacy policy is present but cookie policy and terms of service are missing.
  5. No visible forms or data collection fields on the main page.
  6. No social media links detected in the provided HTML content.
  7. Use of HTTPS and clientTransferProhibited domain status are positive security indicators.
  8. No analytics or tracking scripts detected in the provided HTML.
  9. No advertising or marketing scripts or networks detected.
Technical notes

Notes

The website uses a clean and modern technical stack with Bootstrap for responsive design and SVG for scalable graphics. It is hosted under a reputable registrar with HTTPS enabled, ensuring secure transport. The site lacks a CMS or advanced frameworks, indicating a custom or lightweight implementation. Performance is moderate with no heavy scripts detected. Mobile optimization is good, but accessibility features are basic. SEO is supported by proper meta tags and Open Graph images. No analytics or tracking scripts were found, indicating minimal data collection. The site would benefit from adding security headers and DNSSEC to improve technical security posture.
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. 73/100 −2Medium25 findingsView report
  2. 75/100Medium21 findingsView report
Reviews of this site

Share your experience with trusted-introducer.org. 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 trusted-introducer.org.

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.