Skip to main content

Security report for cert.org

Software Engineering Institute · Government · United States

Medium risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

69/100

Risk levelMedium

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

The Software Engineering Institute's CERT Division, hosted under the domain insights.sei.cmu.edu, is a leading cybersecurity research and operational organization affiliated with Carnegie Mellon University. It provides advanced cybersecurity services including vulnerability research, incident response, workforce development, and risk management. The division collaborates extensively with government, industry, law enforcement, and academia to enhance cybersecurity resilience. The website reflects a mature, professional digital presence with comprehensive content, leadership profiles, case studies, and vulnerability disclosures, positioning it as a trusted authority in cybersecurity. Technically, the website employs modern web technologies such as Vue.js, MathJax, and Font Awesome, and integrates analytics tools like Google Tag Manager and Silktide Analytics. The site is mobile-optimized, accessible, and SEO-friendly, though performance is moderate. Security posture is strong with HTTPS enforced and secure forms, but could be improved by adding security headers and explicit cookie consent mechanisms. Privacy compliance is supported by a comprehensive privacy policy linked from the main SEI site. Overall, the security posture is robust with no detected vulnerabilities or exposed sensitive data. The lack of WHOIS data for the subdomain is typical and not concerning given the affiliation with Carnegie Mellon University. The site maintains high trustworthiness and professionalism, with clear contact information and active social media engagement. Strategically, the CERT Division should enhance privacy compliance by implementing cookie consent banners and publish explicit security policies or security.txt files to facilitate vulnerability reporting. These steps will further strengthen user trust and regulatory compliance.

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

  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 384-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 cert.org

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
57
Security headers
60
Email security
75
DNS health
70
Network security
100
GDPR outside view
53
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention cert.org, from OffSeq Breach.

Total records
176
Employees
0
Customers
176
Third parties
0
Weak passwords
5%

14 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for cert.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The CERT Division operates as an essential government and educational sector entity under Carnegie Mellon University, focusing on cybersecurity research and operational support. Its market position is strong, leveraging the university's reputation and multidisciplinary collaboration. The business model centers on research, training, and cybersecurity services, targeting government agencies, industry partners, and academia. Revenue streams likely include government contracts, grants, and training programs. The division's partnership ecosystem includes vulnerability databases and cybersecurity centers. Growth indicators include active publication of vulnerabilities, case studies, and workforce development initiatives. The organization's operations reflect a strategic focus on advancing cybersecurity resilience and workforce capability.

Security posture

The CERT Division demonstrates a mature security posture with HTTPS enforced and secure form handling including CSRF tokens. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options represents an area for improvement. Privacy compliance is supported by a comprehensive privacy policy, but the lack of a cookie consent mechanism and security.txt file for vulnerability disclosure are gaps. Incident response readiness is implied by the presence of a dedicated vulnerability reporting page. Overall, the security culture appears strong, but formalizing security policies and enhancing privacy mechanisms would improve compliance and trust.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Add a cookie consent banner or mechanism to comply fully with GDPR and other privacy regulations.
  3. Publish a dedicated security policy page detailing security frameworks, certifications, and incident response procedures.
  4. Create and host a security.txt file to facilitate standardized vulnerability disclosure and improve transparency.
  5. Regularly audit and update third-party scripts and analytics tools to ensure no vulnerabilities or privacy issues arise.

Contact details published on the site

Addresses
Legal name
Carnegie Mellon University
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Software Engineering Institute
Description
The Software Engineering Institute is leading and advancing software and cybersecurity to solve the nation's toughest problems.
Key services
Cybersecurity research, Incident response, Vulnerability analysis, Cyber workforce development, Secure development, Risk and resilience management
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Vue.js, MathJax, Font Awesome, Google Tag Manager, Silktide Analytics
Frameworks
Vue.js
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure form with CSRF token

Analytics and tracking

Services
Silktide Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Silktide Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a division page of the Software Engineering Institute at Carnegie Mellon University.
  2. Content is rich with leadership info, services, case studies, and vulnerability disclosures.
  3. No WHOIS data available for the subdomain, which is typical for subdomains under university domains.
  4. No privacy or cookie consent banners detected on this page, but privacy policy is linked on main site.
  5. Uses modern web technologies and analytics tools.
  6. No signs of malicious or suspicious content.
  7. Contact information is clearly provided including phone and physical address.
  8. Social media presence is active and linked.
  9. No security.txt file found for vulnerability disclosure but a dedicated vulnerability reporting page exists.
Technical notes

Notes

The website is built using modern JavaScript frameworks, notably Vue.js, and includes MathJax for mathematical rendering and Font Awesome for icons. It integrates analytics services such as Google Tag Manager and Silktide Analytics for user behavior tracking. The site is mobile responsive and accessible, with good SEO practices including meta tags and Open Graph data. Performance is moderate, likely due to the use of multiple external scripts and rich content. No CMS was explicitly detected, suggesting a custom or university-managed platform. Hosting details are not explicit but likely university infrastructure. Technical risks include the absence of security headers and cookie consent mechanisms, which should be addressed to reduce compliance and security 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

Reviews of this site

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