Skip to main content

Security report for vayamed.com

Vayamed GmbH · Healthcare · Germany

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

Security score

70/100

Risk levelMedium

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

Vayamed GmbH operates as a specialized healthcare provider focusing on medical cannabis therapies, offering high-quality, natural cannabinoid products and expert consultation services primarily to patients, doctors, and pharmacists in Germany. The company is part of the larger Sanity Group, positioning itself as a reputable player in the medical cannabis market with a medium-sized business footprint. Their digital presence is built on WordPress with WooCommerce, integrating modern marketing and consent management tools. However, the website lacks a valid SSL certificate, which critically impacts its security posture. While security headers are partially implemented, the absence of HTTPS and modern TLS protocols exposes the site to significant risks. Privacy compliance is well addressed with clear cookie consent mechanisms and a comprehensive privacy policy. Contact information is prominently displayed, enhancing business credibility. Overall, the site demonstrates good content quality and SEO practices but requires urgent security improvements to protect user data and maintain trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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 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

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

Keep watching vayamed.com

This scan found 16 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
50
Security headers
70
Email security
80
DNS health
85
Network security
90
GDPR outside view
43
Average
70

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

Vayamed's market positioning leverages its affiliation with the Sanity Group, providing a competitive advantage in the medical cannabis sector. Their business model combines product sales with expert advisory services, targeting a niche but growing healthcare segment. The company emphasizes pharmaceutical-grade quality (GMP) and invests in research and development to innovate therapy options. Their digital ecosystem includes partnerships and related domains such as avaay.de, indicating a broader network within the cannabis healthcare industry. Growth indicators include a comprehensive product portfolio and digital consultation offerings. Strategic observations suggest focusing on enhancing digital security and expanding transparent communication around data protection and incident response to strengthen market trust.

Security posture

The current security maturity level is low due to the absence of HTTPS and TLS encryption, which are fundamental for protecting data in transit. The website implements some security headers like X-Frame-Options and X-Content-Type-Options, which mitigate certain attack vectors. No vulnerabilities such as Heartbleed or POODLE were detected, but the lack of SSL/TLS and certificate transparency compliance are critical gaps. There is no visible security policy or incident response information, which limits preparedness and transparency in case of security incidents. GDPR compliance is supported by a privacy policy and cookie consent, but the security posture needs urgent enhancement to align with best practices and regulatory expectations. The business impact of these vulnerabilities includes potential data interception and loss of user trust.

Recommendations

  1. Install and properly configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and configure strong cipher suites to secure communications.
  3. Publish a clear security policy and incident response plan with dedicated contact channels for security issues.
  4. Regularly audit and update security headers and implement session resumption to improve security and performance.
  5. Enhance transparency around data protection practices and provide detailed cookie and privacy information to users.
Technical notes

Notes

The website is built on a WordPress CMS platform with WooCommerce for e-commerce functionality, supported by jQuery and various WooCommerce frontend scripts. SEO is enhanced using Yoast SEO plugin and structured data (JSON-LD) is implemented for better search engine understanding. The site uses Usercentrics for cookie consent management and Google Tag Manager for analytics. Hosting appears to be on a Prometheus server with DNS managed via GoDaddy nameservers. Performance metrics are missing or zero, indicating potential issues with load time measurement or slow response. Mobile optimization is good, but accessibility features are basic. The lack of SSL/TLS is a major technical risk. Modernization opportunities include upgrading security infrastructure, improving performance monitoring, and enhancing accessibility compliance.
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 vayamed.com. 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 vayamed.com.

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.