Skip to main content

Security report for cbl.gov.ly

مصرف ليبيا المركزي · Finance · Libya

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

49/100

Risk levelHigh

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

The Central Bank of Libya (مصرف ليبيا المركزي) operates as an independent financial institution fully owned by the Libyan state, serving as the country's monetary authority. The website reflects a well-established government entity providing comprehensive financial services, including banking supervision, market operations, currency issuance, and economic reporting. The target audience includes Libyan citizens, financial institutions, government bodies, and investors. The business model is that of a central bank with regulatory and operational roles in Libya's financial sector. Technically, the website is built on WordPress CMS with modern front-end technologies such as UIkit and Highcharts for data visualization. It incorporates accessibility features and is optimized for mobile devices, offering a good user experience. The site uses HTTPS and integrates analytics tools like Google Tag Manager and Cloudflare Insights, indicating a moderate level of digital maturity. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. However, it lacks explicit security headers and a published security.txt or vulnerability disclosure policy. Privacy compliance is partial, with a privacy/security policy present but no cookie consent mechanism or GDPR-specific indicators. Contact information is available but no dedicated incident response contacts are published. Overall, the website is professional, trustworthy, and content-rich, suitable for its role as a central bank's official portal. Strategic recommendations include enhancing security headers, publishing vulnerability disclosure and incident response information, and implementing cookie consent to improve privacy compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 100 · Critical
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. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching cbl.gov.ly

This scan found 20 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
0
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
10
Average
49

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

The Central Bank of Libya holds a critical position as the nation's monetary authority, providing regulatory oversight and financial services. Its market position is authoritative within Libya's financial sector. The business model is government-owned and focused on monetary policy, banking supervision, and financial market operations. Revenue streams are typical of central banks, including currency issuance and financial services to government and banks. The website indicates active engagement with stakeholders through reports, policies, and digital services like LYPay. Partnerships with financial intelligence and payment units suggest a collaborative ecosystem. Growth indicators include regular publication of economic data and adoption of electronic payment systems. The presence of a developer portal signals openness to technological innovation.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no visible exposure of sensitive information. The use of security and accessibility plugins suggests attention to security and usability. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options is a gap. There is no visible security.txt or vulnerability disclosure page, limiting transparency for security researchers. Privacy compliance is incomplete due to missing cookie consent mechanisms. Incident response readiness is unclear as no dedicated security contact channels are provided. Overall, the security posture is adequate for a government financial institution but can be improved to meet best practices and compliance standards.

Recommendations

  1. Implement and publish a security.txt file to facilitate vulnerability reporting.
  2. Add and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Introduce a cookie consent banner/mechanism to comply with privacy regulations.
  4. Publish incident response contact information to improve transparency and readiness.
  5. Regularly audit and update third-party plugins and scripts to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
مصرف ليبيا المركزي
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
مصرف ليبيا المركزي
Description
مصرف ليبيا المركزي مؤسسة مالية مُستقلة ومملوكة بالكامل للدولة الليبية، ويُمثَّل السلطة النقدية بها وقد حدد قانون إنشاء المصرف المركزي والقوانين اللاحقة له
Key services
الرقابة المصرفية, عمليات السوق, إصدار العملة, أسعار صرف العملات, الدفع الإلكتروني, التقارير والمنشورات الاقتصادية
Content quality
good
Branding
consistent

Technology

Stack
jQuery, UIkit, Highcharts, WordPress, PHP
Frameworks
WordPress, UIkit
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed credentials in HTML
  • Use of security plugins (implied by WordPress and accessibility plugin)

Analytics and tracking

Services
Google Tag Manager, Cloudflare Insights
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Cloudflare Insights
Marketing tools
AddToAny
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and content-rich
  2. Content is primarily in Arabic with English language option
  3. Strong focus on financial and banking sector information
  4. Includes accessibility tools and features
  5. No visible privacy cookie consent banner
  6. No explicit terms of service page found
  7. Social media presence is official and consistent
  8. Use of modern web technologies and analytics
Technical notes

Notes

The website is built on a WordPress platform enhanced with UIkit for UI components and Highcharts for interactive data visualization. It uses jQuery and several plugins for accessibility and search filtering. The site loads fonts from Google Fonts and uses CDN resources for performance. Analytics are implemented via Google Tag Manager and Cloudflare Insights. The site is mobile-optimized and includes accessibility tools, indicating a focus on usability. Performance is moderate, with some lazy loading and prefetching techniques. Technical risks include reliance on third-party plugins and lack of explicit security headers. Opportunities exist to modernize security practices and improve privacy 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 cbl.gov.ly. 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 cbl.gov.ly.

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.