Skip to main content

Security report for mscare.org

Consortium of Multiple Sclerosis Centers · Healthcare · United States

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

53/100

Risk levelMedium

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

The Consortium of Multiple Sclerosis Centers (CMSC) is a well-established non-profit organization dedicated to advancing clinical research, education, and advocacy in multiple sclerosis care. The website serves healthcare professionals, researchers, patients, and caregivers by providing continuing education, certifications, special interest groups, and annual meetings. CMSC holds a strong market position as a leading North American resource for MS care professionals, supported by partnerships with reputable organizations and a comprehensive offering of services.

Scanned

NIS2 and GDPR posture

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

6 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

    • 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 mscare.org

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
25
Email security
60
DNS health
80
Network security
20
GDPR outside view
70
Average
53

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

CMSC operates a non-profit business model focused on professional development and patient advocacy within the healthcare sector. Its revenue streams likely include membership fees, event registrations, and educational program fees. The organization targets multidisciplinary healthcare providers and MS patients, leveraging partnerships with foundations, scholarly journals, and coalitions to enhance its reach and impact. The website content and structure reflect a mature organization with consistent branding and trust signals such as certifications and professional events.

Security posture

The website demonstrates a good security posture with HTTPS enforced and use of CAPTCHA mechanisms on forms to prevent abuse. However, it lacks several recommended security headers such as Content-Security-Policy and Strict-Transport-Security, which could enhance protection against common web attacks. No vulnerabilities or exposed sensitive data were detected. The absence of a security.txt file and incident response contact information suggests room for improvement in vulnerability disclosure and incident management readiness.

Recommendations

  1. Implement additional HTTP security headers including Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security to strengthen web security.
  2. Add a cookie consent banner and cookie policy page to improve GDPR compliance and user privacy transparency.
  3. Publish a security.txt file to facilitate responsible vulnerability disclosure and improve incident response communication.
  4. Enhance accessibility features to meet recognized standards and improve user experience for all visitors.
  5. Maintain regular updates of WordPress core, plugins, and themes to mitigate risks from known vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Consortium of Multiple Sclerosis Centers
Description
CMSC provides leadership in clinical research and education; develops vehicles to share information and knowledge among members; disseminates information to the health care community and to persons affected by MS.
Key services
Continuing education programs, Certifications for MS specialists, Special interest groups, Annual meetings and conferences, Publications and advocacy
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, WooCommerce, WPBakery Page Builder, jQuery, FontAwesome, Google Fonts, Contact Form 7, Paid Member Subscriptions Pro, Slider Revolution
Frameworks
Bootstrap
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA and Turnstile captcha on forms
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a professional non-profit organization focused on multiple sclerosis care and education.
  2. Content is rich, well-structured, and targeted at healthcare professionals and patients.
  3. No signs of malicious or suspicious activity detected.
  4. WHOIS data is unavailable, likely due to privacy protection or query failure.
  5. Security posture is good but can be improved with additional headers and policies.
  6. No cookie consent mechanism detected, which may affect GDPR compliance.
  7. Multiple external trusted partner domains linked.
  8. No advertising or tracking services detected, indicating privacy-conscious approach.
Technical notes

Notes

The website is built on WordPress CMS with a modern technology stack including WooCommerce, WPBakery Page Builder, and various plugins for membership and forms. It uses Bootstrap for responsive design and FontAwesome for icons. Performance is moderate with good mobile optimization and SEO practices. The site leverages external trusted domains for partnerships and educational content. There is no evidence of heavy tracking or advertising scripts, indicating a privacy-conscious approach. Opportunities exist to improve accessibility and implement advanced security headers.
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 mscare.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 mscare.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.