Skip to main content

Security report for mfda.ca

Canadian Investment Regulatory Organization · Finance · Canada

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

Security score

75/100

Risk levelMedium

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

The Canadian Investment Regulatory Organization (CIRO) operates as a pan-Canadian self-regulatory organization overseeing investment dealers, mutual fund dealers, and trading activities on Canada's debt and equity marketplaces. It aims to promote healthy capital markets through fair and effective regulation, ensuring investor protection and confidence. The website reflects a professional and comprehensive regulatory body with extensive resources for investors, firms, and registered individuals, including educational materials, rule enforcement, and market data transparency. Technically, the website is built on Drupal 10, leveraging modern web technologies such as Google Tag Manager and Modernizr. The site is mobile-optimized, accessible, and SEO-friendly, with a moderate performance profile. Security posture is strong with HTTPS enforced and secure form handling, though explicit security headers could be more visible. Privacy compliance is good with a comprehensive privacy policy, but lacks a visible cookie consent mechanism. Overall, the security posture is solid with no evident vulnerabilities or exposed sensitive data. The domain WHOIS data is unavailable, indicating privacy protection, which is typical for organizations of this nature. The website maintains a high level of professionalism and trustworthiness, supported by clear governance and regulatory transparency. Strategic recommendations include enhancing cookie consent, publishing security policies, and adding vulnerability disclosure mechanisms to further strengthen trust and 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. 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 SSL Key Length

      SSL certificate uses 256-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 mfda.ca

This scan found 19 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
75
Security headers
70
Email security
80
DNS health
70
Network security
100
GDPR outside view
53
Average
75

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

CIRO holds a critical position in the Canadian financial regulatory ecosystem as a self-regulatory organization. Its business model centers on regulatory oversight, investor protection, and market integrity enforcement. The organization targets investors, investment firms, and registered individuals, providing services such as rulemaking, proficiency standards, and trade surveillance. The website's linkage to partner domains like IIROC and MFDA indicates a collaborative regulatory environment. The presence of strategic plans and annual priorities suggests a forward-looking governance approach. The lack of direct contact emails or phone numbers on the site implies a controlled communication channel, likely to maintain regulatory compliance and security.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, secure form handling, and no visible exposure of sensitive data. The use of Google Tag Manager is implemented asynchronously, reducing performance impact. However, explicit security headers such as X-Frame-Options and X-Content-Type-Options are not clearly present in the HTML source, which could be improved. The absence of a published security policy or incident response information limits transparency in security governance. No vulnerability disclosure or security.txt file is found, which is a potential area for enhancement. Overall, the site is secure but could benefit from more explicit security documentation and headers.

Recommendations

  1. Implement and verify explicit security headers including X-Frame-Options and X-Content-Type-Options.
  2. Add a visible cookie consent banner to comply with privacy regulations and improve user transparency.
  3. Publish a formal security policy and incident response plan accessible on the website.
  4. Create and maintain a security.txt file to facilitate vulnerability disclosure and improve security posture.
  5. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Canadian Investment Regulatory Organization
Description
Pan-Canadian self-regulatory organization overseeing investment dealers, mutual fund dealers, and trading activity on Canada's debt and equity marketplaces. Mission to promote healthy capital markets by regulating fairly and effectively to protect investors.
Key services
Regulation of investment dealers and mutual fund dealers, Investor protection and education, Trade surveillance, Rulemaking and enforcement, Proficiency and continuing education for registered individuals
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, Modernizr
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Secure forms with CSRF tokens (implied by Drupal)
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager asynchronously

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

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 rich content and navigation
  2. Uses modern CMS (Drupal 10) and standard web technologies
  3. Strong focus on investor education and regulatory transparency
  4. No direct contact emails or phone numbers found in HTML; contact via form
  5. No explicit cookie consent mechanism detected
  6. WHOIS data unavailable, indicating privacy protection
  7. Social media presence on Facebook, LinkedIn, Twitter (X), and YouTube
  8. No signs of malicious or suspicious content
Technical notes

Notes

The website is powered by Drupal 10, a modern and widely supported CMS, indicating a robust and maintainable technical infrastructure. It uses Google Tag Manager for analytics and tracking, and Modernizr for feature detection, supporting cross-browser compatibility. The site is mobile-optimized with responsive design and accessibility features, enhancing user experience across devices. Performance is moderate, likely due to rich content and media assets. The absence of explicit hosting provider information limits full infrastructure assessment. Overall, the technical stack is modern and well-implemented with opportunities for performance tuning and enhanced security header deployment.
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 mfda.ca. 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 mfda.ca.

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.