Chrome to Turn HTTPS on by Default for Public Sites
Source SecurityWeek
Description
Starting October 2026, the browser will ask users if they want to access public websites that do not use secure connections. The post Chrome to Turn HTTPS on by Default for Public Sites appeared first on SecurityWeek .
Impact
For European organizations, this change will drive a stronger adoption of HTTPS across public websites, improving overall web security and user data protection. Organizations still serving content over HTTP risk losing user trust and traffic due to browser warnings, potentially impacting reputation and business continuity. The enforcement of HTTPS will reduce the risk of data interception and manipulation, enhancing confidentiality and integrity of communications. However, organizations may face operational challenges and costs related to migrating legacy systems, updating certificates, and ensuring compatibility. Regulatory compliance with GDPR and other privacy laws will be supported by this shift, as encrypted communications are a key component of data protection. The impact is particularly significant for sectors with sensitive data or high public interaction, such as finance, healthcare, and e-commerce. While no direct exploit is involved, failure to adapt could indirectly increase vulnerability exposure by encouraging users to bypass warnings or seek less secure alternatives. Overall, the change promotes a safer internet environment but requires proactive organizational response to avoid negative consequences.
Defensive guidance
European organizations should immediately begin auditing their public web services to identify any HTTP-only endpoints and prioritize migration to HTTPS. This includes obtaining and deploying valid TLS certificates from trusted certificate authorities, preferably using automated renewal mechanisms like Let's Encrypt. Web administrators should ensure proper TLS configuration, including strong cipher suites and protocols, to maximize security and compatibility. Organizations should test their websites for mixed content issues that could degrade user experience or trigger browser warnings. User education campaigns can help prepare customers and employees for the upcoming browser changes, reducing confusion and support requests. Monitoring web traffic and error logs will help identify and resolve access issues post-implementation. Additionally, organizations should update internal policies and vendor requirements to mandate HTTPS usage for all public-facing services. Collaboration with web developers and IT teams is essential to ensure a smooth transition before the October 2026 deadline. Finally, organizations should stay informed about browser updates and security best practices to maintain compliance and security posture.
Summary
Google Chrome's upcoming policy change scheduled for October 2026 will prompt users when attempting to access public websites that do not use HTTPS, effectively making HTTPS the default connection method for public sites. This initiative is designed to improve web security by encouraging encrypted communication, thereby protecting users from man-in-the-middle attacks, eavesdropping, and data tampering that are possible over unencrypted HTTP connections. Although this is not a vulnerability or exploit in itself, it represents a significant shift in browser behavior that will impact website accessibility and user experience. Websites that have not yet implemented HTTPS may see increased warnings or user hesitation, potentially reducing traffic and trust. For organizations, this means an imperative to migrate all public-facing web services to HTTPS, including obtaining valid TLS certificates and ensuring proper configuration to avoid mixed content issues. The change aligns with broader industry trends toward securing web traffic and protecting user privacy. Since no specific affected versions or exploits are noted, the threat is more about the operational impact and security posture improvement rather than an immediate attack vector. The medium severity rating reflects the moderate but important impact on confidentiality and integrity by enforcing encryption, with no direct availability impact or exploitation complexity. This policy will affect all public websites accessed via Chrome, which holds a significant market share in Europe, making this a widespread consideration for European web service providers and users.
References
Community reviews
Related threats
- Online ad firm Adform’s script compromised to steal cryptocurrencyBreach
- Read This Before You Buy That TV Streaming StickMalware
- Canada’s Bill C-8 is here: Why the 72-hour reporting rule will redefine critical infrastructure securityCriticalVulnerability
- Russian hackers exploit Exchange OWA zero-day for long-term mailbox accessThreat Actor
- ScreenConnect leveraged in cyberattacks | Kaspersky official blogPhishing