Skip to main content

Security report for bruyere.org

Bruyère Health · Healthcare · Canada

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

Bruyère Health is a leading healthcare organization based in Eastern Ontario, Canada, specializing in aging, rehabilitation, and complex medical care. The organization integrates compassionate, person-centered care with world-class research and education to improve quality of life for patients and their families. It operates multiple care sites and offers a broad range of services including complex continuing care, palliative care, rehabilitation, family medicine, and long-term care. Bruyère Health also emphasizes research and education, collaborating with the University of Ottawa and other partners. The website reflects a mature, well-established non-profit healthcare entity with a strong regional presence and community engagement through volunteering and donations. Technically, the website is built on ASP.NET WebForms with modern JavaScript libraries such as jQuery and MasterSlider for UI components. It employs Google Analytics and Google Tag Manager for analytics and tracking. The site is mobile optimized and accessible, with good SEO practices and clear navigation. However, some legacy technologies and lack of visible security headers suggest room for modernization. Security posture is solid with HTTPS enforced and no visible sensitive data exposure. However, the absence of explicit security headers and cookie consent mechanisms indicates areas for improvement in compliance and security best practices. WHOIS data is unavailable, likely due to privacy protection, which is common for healthcare organizations to protect sensitive registrant information. Overall, Bruyère Health's website is professional, trustworthy, and well-aligned with its healthcare mission. Strategic enhancements in privacy compliance, security policies, and technical modernization would further strengthen its digital maturity and user trust.

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

This scan found 22 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
62
Security headers
55
Email security
80
DNS health
85
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

Bruyère Health holds a strong market position as a leading healthcare provider in Eastern Ontario, focusing on aging populations and complex care needs. Its non-profit business model is supported by donations, government funding, and partnerships with academic institutions. The organization leverages research and education to drive innovation and quality improvement in healthcare delivery. Its target customers include patients, families, healthcare professionals, volunteers, and researchers. The website indicates active community engagement and transparency through public reporting and accessible information. Partnerships with the University of Ottawa and use of third-party platforms for donations and employee management reflect a collaborative ecosystem. Growth indicators include ongoing research initiatives, educational placements, and community events. The organization's branding and content consistently reinforce its mission and values, supporting strong business credibility.

Security posture

The website demonstrates a mature security posture with HTTPS enforced site-wide and no visible exposure of sensitive information in the HTML content. Use of Google Tag Manager and Analytics is implemented with asynchronous loading to minimize performance impact. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces defense-in-depth. No explicit cookie consent or privacy banners were detected, which may impact GDPR compliance. There is no published security policy or incident response contact information, limiting transparency for security incidents. No known vulnerable libraries or scripts were identified. Overall, the security posture is good but could be enhanced by implementing recommended headers, privacy mechanisms, and publishing security policies to improve compliance and user 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 with GDPR and other privacy regulations, clearly informing users about tracking and data usage.
  3. Publish a dedicated security policy and incident response contact information on the website to improve transparency and preparedness.
  4. Conduct regular security audits of third-party scripts and libraries to ensure no vulnerabilities are introduced via dependencies.
  5. Plan for modernization of legacy ASP.NET WebForms technology to improve maintainability, performance, and security posture.

Contact details published on the site

Addresses
Legal name
Bruyère Health
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bruyère Health
Description
Bruyère Health is Eastern Ontario’s leading health organization specializing in aging, rehabilitation, and care for those with multiple complex medical conditions. We bring together compassionate, person-centred care with world-class research to maximize quality of life for those we care for and their loved ones.
Key services
Complex Continuing Care, Palliative Care, Rehabilitation, Family Medicine, Transitional Care, Long-term Care, Research, Education, Volunteering, Public Reporting
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery 3.7.1, Google Analytics, MasterSlider, Font Awesome 4.7.0, ASP.NET WebForms, PIE.htc for CSS3 compatibility, bxSlider
Frameworks
ASP.NET WebForms
Platforms
Windows Server (implied by ASP.NET)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager and Analytics with async loading
  • No visible vulnerable libraries

Analytics and tracking

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

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. Content is professionally presented and well structured
  3. Strong focus on healthcare services, research, education, and community support
  4. Multiple external trusted domains linked for donations, social media, and employee resources
  5. No visible security policy or incident response contact information
  6. No cookie consent banner detected despite use of tracking scripts
  7. WHOIS data is unavailable, likely due to privacy protection
  8. Use of ASP.NET WebForms technology indicates legacy but maintained platform
  9. Good mobile optimization and accessibility features observed
Technical notes

Notes

The website is built on ASP.NET WebForms, a mature but legacy web framework, combined with modern JavaScript libraries such as jQuery 3.7.1, MasterSlider for image sliders, and bxSlider for news carousels. Font Awesome 4.7.0 is used for iconography. Google Fonts are loaded for typography. Google Analytics and Google Tag Manager are integrated for analytics and event tracking, including donation button clicks. The site uses CSS normalization and skeleton CSS frameworks for responsive design. The presence of PIE.htc indicates support for legacy IE browsers. The site is mobile optimized with responsive menus and accessible navigation. Performance is moderate with asynchronous script loading but could benefit from further optimization. No CMS was detected, suggesting a custom or proprietary platform. Hosting provider details are not evident from the content. Overall, the technical infrastructure is stable but shows signs of legacy technology that could be modernized for improved performance and security.
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 bruyere.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 bruyere.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.