Skip to main content

Security report for concrete5.org

Concrete CMS · Technology · N/a

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

Security score

81/100

Risk levelLow

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

Concrete CMS is an open source content management system designed for teams including content creators, designers, and developers. The company offers a website builder with built-in tools to simplify content editing and management. It serves a diverse audience including enterprise clients such as the U.S. Army and BASF, positioning itself as a trusted and secure CMS provider. The business model combines open source software with hosting and support services, emphasizing security compliance with certifications like ISO 27001, SOC 2, and HIPAA. The website demonstrates a professional and consistent brand presence with comprehensive content and clear navigation. Technically, the site leverages Concrete CMS as its core platform, augmented by modern web technologies including jQuery, Bootstrap, FontAwesome, and multiple analytics and marketing tools such as Google Tag Manager, Matomo, ZoomInfo, and Pipedrive LeadBooster. The site is mobile-optimized and performs moderately well, with good SEO and accessibility features. Security posture is strong with HTTPS enforced and compliance certifications highlighted, though HTTP security headers are not explicitly detected in the provided data. The security evaluation reveals robust best practices including role-based access control, workflow approvals, and version control. However, the absence of explicit incident response contact details and a security.txt file are gaps. The WHOIS data is missing, which raises concerns about domain transparency and legitimacy, although the website content and client references strongly support authenticity. Overall, the site scores well on content quality, technical implementation, and security, with room for improvement in privacy compliance and business credibility transparency. Strategic recommendations include implementing HTTP security headers, publishing a vulnerability disclosure policy, enhancing incident response contact visibility, auditing third-party scripts regularly, and clarifying data retention policies to strengthen trust and compliance.

Scanned

This is an earlier scan of concrete5.org. View the latest report

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

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

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
100
Security headers
65
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
81

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

Concrete CMS occupies a competitive position in the open source CMS market, targeting teams and enterprises requiring secure, compliant, and easy-to-use content management solutions. Its competitive advantages include strong security certifications, enterprise client endorsements, and a comprehensive hosting and support ecosystem. Revenue streams likely derive from hosting subscriptions, custom SLAs, and professional services. The target customer segments include government, finance, manufacturing, healthcare, and education sectors. Growth indicators include recent blog activity and ongoing feature development. The partnership ecosystem includes community forums, documentation, and marketplace integrations, supporting a vibrant user and developer community. Operationally, the company demonstrates maturity with a focus on security and compliance, positioning it well for regulated industries.

Security posture

The security maturity level of Concrete CMS is high, supported by ISO 27001 certification and SOC 2 and HIPAA compliant hosting options. The platform incorporates role-based access control, workflow approvals, and version control to ensure content integrity and controlled access. No critical vulnerabilities or exposed sensitive data were detected in the analysis. Compliance with GDPR is indicated by the presence of a privacy policy and cookie consent mechanism. However, the absence of a published security.txt file and explicit incident response contact information represents a compliance gap. The use of multiple third-party tracking and marketing scripts necessitates ongoing security audits to mitigate supply chain risks. Overall, the security culture appears strong but could benefit from enhanced transparency and formalized vulnerability disclosure processes.

Recommendations

  1. Implement HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a security.txt file and clearly display incident response contact information to facilitate responsible vulnerability disclosure and improve trust.
  3. Conduct regular security audits of third-party scripts and dependencies to identify and mitigate potential vulnerabilities.
  4. Clarify and publicly document data retention policies and privacy compliance measures to strengthen GDPR adherence and user trust.
  5. Enhance business credibility by providing verified contact information such as company emails and phone numbers on the website.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Concrete CMS
Description
Concrete CMS is an open source content management system for teams. A website builder with built in tools make editing content easy.
Key services
Content Management System, Website Builder, Hosting Services, Support and Training
Content quality
excellent
Branding
consistent

Technology

Stack
Concrete CMS, jQuery, Bootstrap, FontAwesome, Google Tag Manager, Matomo Analytics, Pipedrive LeadBooster, ZoomInfo Pixel, LeadFeeder
Frameworks
Concrete CMS
Platforms
Web
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ISO 27001 certified security
  • SOC 2 and HIPAA compliant hosting
  • Role-based access control
  • Workflow approvals
  • Version control

Analytics and tracking

Services
Google Analytics, Matomo Analytics, ZoomInfo, LeadFeeder
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
ZoomInfo, LeadFeeder, Pipedrive LeadBooster
Marketing tools
Matomo Analytics, Pipedrive LeadBooster
Transparency
good

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 no blocking detected.
  2. Strong emphasis on security certifications and compliance.
  3. Multiple trusted enterprise clients referenced.
  4. Comprehensive navigation with clear business focus.
  5. Use of multiple third-party analytics and marketing tools.
  6. No direct contact emails or phone numbers found on homepage.
  7. WHOIS data missing, which reduces domain transparency.
Technical notes

Notes

The website infrastructure is built on Concrete CMS, a specialized open source content management system. The technology stack includes jQuery, Bootstrap, FontAwesome, and various analytics and marketing tools, indicating a modern and feature-rich environment. Performance is moderate with good mobile optimization and accessibility features. The site uses HTTPS exclusively, ensuring encrypted communications. However, the lack of detected HTTP security headers suggests potential technical debt in security hardening. The presence of multiple third-party tracking scripts introduces a risk vector that requires ongoing management. Overall, the technical implementation is solid but could be improved by adopting additional security best practices and enhancing transparency around hosting and infrastructure.
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

Earlier scans of this domain

  1. 81/100Low23 findingsView report
Reviews of this site

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