Skip to main content

Security report for confidentialcomputing.io

The Linux Foundation · Technology · United States

Medium risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

69/100

Risk levelMedium

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

The Confidential Computing Consortium website is a professionally designed platform hosted by The Linux Foundation, focusing on advancing confidential computing technologies. The consortium serves as an industry collaboration hub, promoting hardware-based trusted execution environments and related security technologies. The website targets technology companies, developers, and security professionals interested in confidential computing. The business model is that of a consortium facilitating standards development and community building. Technically, the website is built on WordPress with integrations of HubSpot for marketing and analytics, Google Tag Manager, and New Relic for performance monitoring. The site uses modern web technologies and is mobile optimized, though accessibility features are basic. Performance is moderate, with room for improvement in SEO and accessibility. From a security perspective, the site uses HTTPS and has domain transfer protections in place. However, DNSSEC is not enabled, and no explicit security headers were detected in the provided data. There is no visible security policy, incident response information, or vulnerability disclosure program, which are areas for improvement. The domain WHOIS data is consistent and transparent, registered to The Linux Foundation, matching the website's claims. Overall, the website presents a trustworthy and credible front for the consortium but would benefit from enhanced privacy compliance, explicit security policies, and improved security headers to strengthen its security posture and user trust.

Scanned

NIS2 and GDPR posture

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

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

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

Keep watching confidentialcomputing.io

This scan found 24 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
85
Security headers
25
Email security
60
DNS health
75
Network security
100
GDPR outside view
68
Average
69

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 Confidential Computing Consortium is positioned as a leading industry consortium in the confidential computing space, backed by The Linux Foundation. Its competitive advantage lies in its collaborative approach to advancing confidential computing standards and technologies. The consortium operates on a membership and partnership model, engaging technology companies and developers. Revenue streams likely include membership fees and sponsorships. The target customers are enterprises and technology providers interested in data security and privacy. The consortium's partnership ecosystem includes major industry players, though specific partners are not listed on the homepage. The organization's operations reflect a mature, well-structured industry initiative with a focus on advocacy and education.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain transfer protections. However, the absence of DNSSEC, security headers, and published security policies indicates gaps in security best practices. No vulnerabilities or exposed sensitive data were detected in the analysis. Compliance with GDPR and other privacy regulations is not clearly demonstrated due to missing privacy and cookie policies. Incident response readiness and security culture indicators are not visible. The site would benefit from implementing security headers, publishing a security policy, and establishing a vulnerability disclosure program to enhance its security posture.

Recommendations

  1. Enable DNSSEC to improve DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a comprehensive privacy policy and cookie policy with clear GDPR compliance statements.
  4. Establish and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Add explicit incident response contact information and security policy details to build user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
The Linux Foundation
Description
The Confidential Computing Consortium is an initiative hosted by The Linux Foundation focused on advancing confidential computing technology to protect data in use. It is a collaborative effort among industry leaders to promote hardware-based trusted execution environments and related technologies.
Key services
Industry collaboration, Standards development, Community building, Educational resources
Content quality
good
Branding
consistent

Technology

Stack
WordPress, HubSpot (analytics, messaging, ads pixel), Google Tag Manager, New Relic Browser monitoring, FontAwesome, Google Fonts (Open Sans)
Frameworks
WordPress CMS, Events Calendar Pro plugin
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status

Analytics and tracking

Services
HubSpot Analytics, Google Tag Manager, New Relic Browser
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
HubSpot Ads
Tracking pixels
HubSpot Ads Pixel, New Relic Browser Agent
Marketing tools
HubSpot
Transparency
basic

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 maintained.
  2. Content is focused on confidential computing technology and industry collaboration.
  3. No direct contact emails or phone numbers found on the homepage HTML.
  4. No explicit privacy, cookie, or terms of service pages detected in the provided HTML.
  5. Use of multiple third-party analytics and marketing tools including HubSpot and New Relic.
  6. No security.txt or vulnerability disclosure information found.
  7. Domain WHOIS data is transparent and consistent with the Linux Foundation ownership.
  8. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on WordPress with a modern tech stack including HubSpot for marketing automation and analytics, Google Tag Manager, and New Relic for performance monitoring. The site uses FontAwesome and Google Fonts for UI elements. Hosting and DNS are managed by reputable providers. Performance is moderate with good mobile optimization but basic accessibility features. SEO is adequately addressed with meta tags and structured data. Technical debt appears low, but improvements in security configurations and privacy compliance are recommended to reduce risk and enhance user trust.
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 confidentialcomputing.io. 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 confidentialcomputing.io.

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.