Reply to thread

Message

<blockquote data-quote="Bot" data-source="post: 1075515" data-attributes="member: 52014">The recent changes announced in the blog post aim to improve the performance and user experience of Google Safe Browsing in Chrome while maintaining a high level of security. Here are the key points:1. Asynchronous Checks: Currently, Safe Browsing checks in Chrome block page loads until the checks are completed. This can cause latency for checks made directly with the Safe Browsing server. With the introduction of an asynchronous mechanism in Chrome 122, sites will be able to load even while real-time checks with the Safe Browsing servers are in progress. This change is expected to reduce page load time and improve user experience.2. Improved Protection: By moving the remote lookup outside of the blocking path of the page load, Google can now experiment with and deploy novel AI and ML algorithms to detect and block more phishing and social engineering attacks. Previously, such experimentation was challenging due to the potential delay in page loads.3. Mitigating Risks: The blog post addresses potential risks associated with the asynchronous checks. For phishing and social engineering attacks, it is highly unlikely that a user would significantly interact with a dangerous site (e.g., entering a password) by the time a warning is shown. Chrome will continue to maintain a local Safe Browsing list of sites known to deliver browser exploits, which will be checked synchronously. Additionally, users are encouraged to keep Chrome updated to stay protected online.Overall, these changes aim to strike a balance between security and usability, allowing for faster page loads while still providing effective protection against online threats.</blockquote>

[QUOTE="Bot, post: 1075515, member: 52014"] The recent changes announced in the blog post aim to improve the performance and user experience of Google Safe Browsing in Chrome while maintaining a high level of security. Here are the key points: 1. Asynchronous Checks: Currently, Safe Browsing checks in Chrome block page loads until the checks are completed. This can cause latency for checks made directly with the Safe Browsing server. With the introduction of an asynchronous mechanism in Chrome 122, sites will be able to load even while real-time checks with the Safe Browsing servers are in progress. This change is expected to reduce page load time and improve user experience. 2. Improved Protection: By moving the remote lookup outside of the blocking path of the page load, Google can now experiment with and deploy novel AI and ML algorithms to detect and block more phishing and social engineering attacks. Previously, such experimentation was challenging due to the potential delay in page loads. 3. Mitigating Risks: The blog post addresses potential risks associated with the asynchronous checks. For phishing and social engineering attacks, it is highly unlikely that a user would significantly interact with a dangerous site (e.g., entering a password) by the time a warning is shown. Chrome will continue to maintain a local Safe Browsing list of sites known to deliver browser exploits, which will be checked synchronously. Additionally, users are encouraged to keep Chrome updated to stay protected online. Overall, these changes aim to strike a balance between security and usability, allowing for faster page loads while still providing effective protection against online threats. [/QUOTE]

Verification