Skip to main content

Security report for concretecms.com

PortlandLabs · 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 established open source content management system designed for teams including content creators, developers, and designers. The platform offers a robust website builder with built-in tools to simplify content editing and management. PortlandLabs, the company behind Concrete CMS, positions itself strongly in the technology sector with a focus on enterprise and government clients, including the U.S. Army. The business model includes open source software distribution, hosting services, and a marketplace for themes, add-ons, and integrations. The website demonstrates excellent content quality, professional design, and clear navigation, targeting professional teams and organizations seeking secure and compliant CMS solutions. Technically, the website employs modern web technologies such as jQuery, Vue.js, Bootstrap, and Moment.js, running on the Concrete CMS platform. It integrates multiple analytics and marketing tools including Google Analytics, Matomo, ZoomInfo, and Pipedrive LeadBooster. The site is mobile optimized and accessible, with good SEO practices evident from meta tags and structured data. Hosting appears to be managed by PortlandLabs with offerings ranging from starter plans to custom enterprise SLAs. Security posture is strong with HTTPS enforced and certifications including ISO 27001, SOC 2, and HIPAA compliance prominently featured. The platform supports role-based access control, workflow approvals, and version control to enhance security and collaboration. However, the site lacks explicit HTTP security headers and a published vulnerability disclosure or security.txt file, which are recommended for further strengthening security transparency. Overall, the website is trustworthy and professional with high-quality content and a mature technical infrastructure. The main risk factor is the absence of WHOIS domain registration data, which is unusual for a business of this profile and slightly reduces trust. Strategic recommendations include implementing security headers, publishing incident response contacts, and enhancing transparency on data retention and vulnerability disclosures.

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 concretecms.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. 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
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 with a focus on team collaboration and enterprise-grade security. Its competitive advantages include built-in robust features requiring minimal extensions, strong security certifications, and a flexible hosting model. Revenue streams likely include hosting subscriptions, marketplace sales of themes and add-ons, and custom development services. The target customer segments are professional teams, enterprises, and government organizations requiring secure, compliant, and easy-to-use CMS solutions. Growth indicators include recent awards and active community engagement. The partnership ecosystem includes integrations with third-party services and a marketplace for extensions. The company maintains a strong market presence with notable clients and a clear brand identity.

Security posture

The security maturity level of Concrete CMS is high, supported by ISO 27001 certification and compliance with SOC 2 and HIPAA standards. The platform incorporates advanced access controls, workflow approvals, and version control to ensure content integrity and security. No vulnerabilities or exposed sensitive data were detected in the website content. However, the absence of HTTP security headers and a public vulnerability disclosure policy indicates room for improvement in security transparency and defense-in-depth. Incident response readiness is not explicitly documented on the site, which could be enhanced to improve trust and preparedness. Overall, the security culture appears strong, especially given the platform's adoption by the U.S. Army and other enterprise clients.

Recommendations

  1. Implement HTTP security headers such as Content Security Policy (CSP), Strict-Transport-Security (HSTS), X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a vulnerability disclosure policy or security.txt file to provide clear guidance for reporting security issues and improve transparency.
  3. Add explicit incident response contact information on the website to facilitate timely communication in case of security incidents.
  4. Regularly audit and update third-party scripts and analytics tools to minimize potential vulnerabilities from external dependencies.
  5. Enhance privacy and data protection transparency by detailing data retention policies and compliance measures in accessible documentation.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PortlandLabs
Description
Concrete CMS is an open source content management system designed for teams, enabling content creators, designers, and developers to build, author, and publish content easily with built-in tools and features.
Key services
Content management system, Hosting services, Marketplace for themes, add-ons, and integrations, Custom development and enterprise hosting
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Vue.js, Bootstrap, Moment.js
Frameworks
Concrete CMS
Performance
moderate
Mobile
good
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 and version control

Analytics and tracking

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

Advertising

Tracking pixels
ZoomInfo, LeadBooster (Pipedrive), Matomo
Marketing tools
Matomo, 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 professional design.
  2. Strong emphasis on security certifications and compliance.
  3. Multiple customer testimonials and enterprise clients featured.
  4. Use of modern web technologies and analytics tools.
  5. No exposed sensitive data or security issues detected in content.
  6. WHOIS data missing, which is a concern but not critical given other trust signals.
Technical notes

Notes

The website is built on Concrete CMS, leveraging modern JavaScript libraries including jQuery and Vue.js, and styled with Bootstrap for responsive design. The presence of Moment.js indicates date/time handling capabilities. The site loads multiple asynchronous analytics and marketing scripts, which may impact performance but provide valuable user insights. The HTML structure is valid and SEO optimized with meta tags, Open Graph, and JSON-LD structured data. Mobile optimization and accessibility are well addressed. Hosting is managed with options ranging from starter plans to custom enterprise SLAs, indicating scalable infrastructure. Technical risks include reliance on multiple third-party scripts and lack of HTTP security headers, which should be addressed to reduce attack surface and improve security posture.
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 concretecms.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 concretecms.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.