Skip to main content

Security report for bcbssc.com

BlueCross BlueShield of South Carolina · Healthcare · United States

Medium risk. 5 critical or high findings in Security headers and GDPR outside view.

Security score

61/100

Risk levelMedium

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

BlueCross BlueShield of South Carolina is a major regional health insurance provider offering a wide range of health insurance products including individual, family, Medicare, and group health plans. The company serves individuals, families, employers, healthcare providers, and agents primarily in South Carolina. The website reflects a well-structured and professionally branded digital presence consistent with its market position as an independent licensee of the Blue Cross Blue Shield Association. Key services include member management, provider resources, employer services, and agent support. The site integrates multiple external partners and resources to support its offerings. Technically, the website employs modern JavaScript frameworks such as Vue.js and Bootstrap Vue, hosted on IBM WebSphere Portal infrastructure with DNS hosted by Level3. Despite the modern tech stack, the site suffers from slow performance with a page load time exceeding 8 seconds and a large page size. Mobile optimization is good, and SEO practices are adequately implemented. However, the site lacks a valid SSL certificate and does not enable HTTPS, which is a critical security flaw. Security headers are absent, and no advanced TLS protocols or HSTS are configured, exposing the site to potential risks. From a security perspective, the site has strong email authentication with valid SPF and DMARC policies, but the absence of HTTPS and security headers significantly lowers its security posture. No vulnerability disclosure or incident response information is publicly available. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism detected. The site uses multiple analytics and marketing tools including Google Analytics, Adobe Launch, and Qualtrics, indicating moderate user tracking. Overall, the website is professionally designed and content-rich but requires urgent security improvements, especially regarding SSL/TLS implementation and security headers. Enhancing privacy compliance and adding explicit cookie consent would further improve trust. Strategic recommendations include immediate SSL certificate installation, enabling modern TLS protocols, implementing security headers, and publishing a vulnerability disclosure policy to strengthen security culture and compliance.

Scanned

NIS2 and GDPR posture

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

5 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 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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching bcbssc.com

This scan found 15 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
50
Security headers
65
Email security
50
DNS health
75
Network security
100
GDPR outside view
25
Average
61

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

BlueCross BlueShield of South Carolina holds a strong market position as a leading health insurance provider in South Carolina, leveraging the trusted Blue Cross Blue Shield brand. Its business model focuses on diversified health insurance products catering to individuals, families, employers, and healthcare providers. Revenue streams likely include premiums from various insurance plans and partnerships with healthcare service providers. The company targets a broad customer base including individual consumers, small and large employers, and insurance agents. The website's integration with partners such as Benefitfocus, Express Scripts, EyeMed, and state government entities reflects a robust partnership ecosystem supporting comprehensive healthcare services. Growth indicators include digital tools like My Health Toolkit and multiple member engagement channels. The company demonstrates strategic alignment with healthcare industry standards and accreditation (URAC).

Security posture

The current security posture of the website is weak due to the lack of a valid SSL certificate and absence of HTTPS enforcement, which is a critical vulnerability exposing users to data interception risks. While email authentication mechanisms such as SPF and DMARC are properly configured, the lack of security headers and modern TLS protocols further weakens the security stance. No public incident response or vulnerability disclosure policies are found, indicating limited transparency and preparedness for security incidents. The site does not implement cookie consent mechanisms, which may impact privacy compliance. Overall, the security maturity level is low, with significant gaps that could impact user trust and regulatory compliance.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable all insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Add essential security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  5. Publish a security.txt file and a clear vulnerability disclosure policy to improve transparency and incident response readiness.
  6. Implement a cookie consent mechanism to comply with privacy regulations and improve user trust.
  7. Optimize website performance to reduce load times and improve user experience.
  8. Enhance accessibility features to meet WCAG standards for broader user inclusivity.
Technical notes

Notes

The website is built on IBM WebSphere Portal CMS and uses a modern front-end stack including Vue.js and Bootstrap Vue for responsive design. It integrates multiple third-party services such as Adobe Launch for tag management, Google Analytics for tracking, Qualtrics for surveys, and Zmags for digital publishing. DNS is managed via Level3, and email authentication is robust with SPF and DMARC policies. However, the absence of a valid SSL certificate and disabled TLS protocols represent critical technical debt and security risks. Performance is suboptimal with a slow page load time and a large page size, indicating potential for optimization. The site demonstrates good mobile optimization and SEO practices but lacks advanced security configurations and privacy compliance mechanisms.
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 bcbssc.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 bcbssc.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.