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. It offers a website builder with built-in tools to simplify content editing and management. The company behind Concrete CMS, PortlandLabs, positions itself as a provider of secure, compliant, and enterprise-ready CMS solutions, serving notable clients such as the U.S. Army, BASF, and Home Depot. Their business model includes offering the open source CMS software alongside hosting, support, and custom development services. The website demonstrates strong branding consistency, professional design, and clear navigation, targeting medium-sized to enterprise organizations in technology and government sectors. Technically, the website leverages modern web technologies including jQuery, Bootstrap, Vue.js, and integrates analytics and marketing tools such as Google Tag Manager, Matomo, ZoomInfo, Leadfeeder, and Pipedrive LeadBooster. The CMS platform itself is Concrete CMS, hosted likely by PortlandLabs. The site is mobile optimized and performs moderately well, with good SEO and accessibility features. From a security perspective, Concrete CMS emphasizes compliance with ISO 27001, SOC 2, and HIPAA standards, offering role-based access control, workflow approvals, and version control. The site uses HTTPS and has cookie consent mechanisms. However, explicit security headers are not detected, and there is no public vulnerability disclosure or incident response contact information, which are areas for improvement. Overall, the website is professional, trustworthy, and content safe for general audiences. The main concern is the lack of WHOIS registration data, which raises questions about domain legitimacy despite the strong business presence. Strategic recommendations include improving security header implementation, publishing vulnerability disclosure policies, and clarifying domain registration details to enhance 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

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 operates in the competitive open source CMS market, differentiating itself through ease of use, robust security certifications, and enterprise-grade hosting options. Its partnerships and client base include government and large corporate entities, indicating a strong market position. The business model combines free open source software with paid hosting, support, and custom development services, enabling diversified revenue streams. The company targets professional teams requiring secure, compliant, and collaborative content management solutions. Growth indicators include recent awards and active community engagement. The ecosystem includes related domains for community, marketplace, documentation, and forums, supporting a comprehensive user experience.

Security posture

The security posture of Concrete CMS is mature, with adherence to recognized standards such as ISO 27001, SOC 2, and HIPAA compliance for hosting. The platform supports granular access controls, workflow approvals, and audit trails, enhancing operational security. The website enforces HTTPS and cookie consent, reflecting privacy awareness. However, the absence of explicit security headers and public vulnerability disclosure policies limits transparency and may expose the platform to certain risks. No incident response contacts are publicly available, which could delay response to security events. Overall, the security maturity is good but could be improved by adopting additional best practices and transparency measures.

Recommendations

  1. Implement and enforce security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a formal vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve transparency.
  3. Provide clear incident response contact information on the website to facilitate timely communication in case of security incidents.
  4. Verify and update WHOIS domain registration information to ensure domain legitimacy and build trust with users and partners.
  5. Enhance privacy compliance disclosures by detailing data retention policies and user rights in alignment with GDPR and other regulations.
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
jQuery, Bootstrap, Vue.js, Google Tag Manager, Matomo Analytics, Pipedrive LeadBooster, ZoomInfo Pixel, Leadfeeder
Frameworks
Concrete CMS
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 and audit logs

Analytics and tracking

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

Advertising

Tracking pixels
ZoomInfo, Leadfeeder, Pipedrive LeadBooster
Marketing tools
Matomo Analytics
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 professional design
  2. Strong emphasis on security certifications and compliance
  3. Multiple customer testimonials and case studies with reputable organizations
  4. Use of modern web technologies and analytics tools
  5. No direct company contact emails or phone numbers found on homepage
  6. WHOIS data missing, which is a concern for domain legitimacy
  7. Cookie consent and privacy policies are implemented
  8. No explicit vulnerability disclosure or incident response contacts published
Technical notes

Notes

The website is built on Concrete CMS, utilizing a modern technology stack including jQuery, Bootstrap, and Vue.js for frontend interactivity. It integrates multiple analytics and marketing tools such as Google Tag Manager, Matomo, ZoomInfo, Leadfeeder, and Pipedrive LeadBooster, indicating a mature digital marketing approach. The site is mobile responsive with good accessibility and SEO optimization. Performance is moderate, with potential for improvement through optimization of third-party scripts. The technical infrastructure supports enterprise and government clients, with hosting likely managed by PortlandLabs. Opportunities exist to modernize security configurations and improve transparency around vulnerability management.
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.