Skip to main content

Security report for cloudnative-pg.io

CloudNativePG · Technology · United States

Medium risk. 9 critical or high findings in Email security, Security headers and 1 other check.

Security score

59/100

Risk levelMedium

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

CloudNativePG is an open source Kubernetes operator designed to manage highly available PostgreSQL clusters with native streaming replication. The project is community-driven and originally created by EnterpriseDB, now under LF Projects, LLC. It targets Kubernetes users and DevOps professionals seeking automated, cloud native PostgreSQL lifecycle management. The website presents comprehensive technical content describing features such as autopilot deployment, data persistence, security, high availability, disaster recovery, monitoring, and advanced architectures. The site is well structured, mobile optimized, and uses modern technologies including Hugo and Google Analytics. Security posture is good with HTTPS and no exposed sensitive data, though explicit security headers and policies are missing. Privacy and cookie policies are absent, indicating compliance gaps. WHOIS data is consistent and transparent, supporting legitimacy. Overall, the website is professional and trustworthy but could improve privacy compliance and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…
  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

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

Keep watching cloudnative-pg.io

This scan found 25 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
95
Security headers
15
Email security
40
DNS health
70
Network security
100
GDPR outside view
35
Average
59

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

CloudNativePG occupies a niche in the cloud native database operator market, focusing on PostgreSQL on Kubernetes. Its open source model with Apache 2 license encourages community contributions and adoption. The project benefits from EnterpriseDB's initial development and Linux Foundation stewardship, enhancing credibility. The business model centers on community-driven development with potential enterprise support. Target customers include cloud native developers, database administrators, and DevOps teams. The partnership ecosystem includes EnterpriseDB and Linux Foundation. Growth indicators include recent domain registration and active GitHub presence. The website content supports technical decision makers evaluating Kubernetes database solutions.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and no visible sensitive data leaks. The product supports TLS encryption, client authentication, and auditing features. However, the website lacks published privacy and cookie policies, security.txt, and incident response contacts, which are important for compliance and trust. No security headers were detected in the HTML. Google Analytics is used without a consent mechanism, raising privacy concerns. No forms or inputs reduce attack surface. Overall, security maturity is good but could be enhanced by formal policies and headers.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance.
  2. Implement a cookie consent mechanism to inform users about tracking.
  3. Add security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options.
  4. Provide a security.txt file or vulnerability disclosure policy with contact information.
  5. Include contact details or a dedicated security contact email for incident response.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
CloudNativePG
Description
CloudNativePG is a Kubernetes operator that manages the full lifecycle of highly available PostgreSQL database clusters with primary/standby architecture using native streaming replication. It automates deployment and management, supports data persistence, security, high availability, disaster recovery, monitoring, advanced architectures, and declarative Postgres operations.
Key services
PostgreSQL cluster lifecycle management, Automated failover and high availability, TLS security and certificate management, Disaster recovery with continuous backup, Monitoring with Prometheus exporter, Declarative Postgres operations, Advanced architectures including connection pooling and multi-region disaster recovery
Content quality
good
Branding
consistent

Technology

Stack
Kubernetes, PostgreSQL, Hugo static site generator, Google Fonts, GitHub buttons, Google Analytics (gtag.js)
Platforms
Kubernetes
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by URL)
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected
  • No forms collecting sensitive data
  • TLS certificate support described for PostgreSQL connections

Analytics and tracking

Services
Google Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
GitHub buttons
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. No privacy or cookie policies found, indicating potential compliance gaps.
  3. No contact emails or phone numbers explicitly provided on the site.
  4. Strong open source and community trust signals present.
  5. Technical content is well structured and relevant to Kubernetes and PostgreSQL users.
  6. Security best practices are described for the product but not fully reflected in website policies.
  7. Google Analytics is used but no cookie consent mechanism is present.
  8. No forms or data collection fields detected on the site.
  9. WHOIS data is transparent and consistent with the business.
Technical notes

Notes

The website is built using the Hugo static site generator, ensuring fast performance and good SEO. It uses Google Fonts and Google Analytics for typography and analytics respectively. Hosting is likely on AWS based on DNS nameservers. The site is mobile responsive with clear navigation and consistent branding. No CMS vulnerabilities or outdated libraries were detected. The absence of forms reduces risk exposure. The technical stack aligns well with the target audience of Kubernetes and PostgreSQL users. Opportunities exist to improve security headers and privacy compliance to reduce risk and enhance trust.
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 cloudnative-pg.io. 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 cloudnative-pg.io.

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.