CyberSecurity 1 : Chrome Tools
Chrome Tools
操作方式 operation method
功能介绍
Technical meal addition:Why Chrome Always Update ?
Chrome 142 has added a local system access protection mechanism. When an external website attempts to access devices such as routers and printers corresponding to local IP segments like 127.0.0.0/8, the browser will pop up a confirmation prompt, and access is only allowed after user authorization. This is to defend against the infringement of local devices by cross-site request forgery attacks.
Strict extension management: Chrome restricts users to installing extensions only from the official store, and version 142 will automatically disable extensions that violate the App Store policies, such as plugins with metadata manipulation or potential vulnerabilities. Users can also manually manage extension permissions, for example, revoking the "read browsing history" permission of ad-blocking tools to prevent such tools from leaking personal data.
Safe Browsing and HTTPS Enhancement: Chrome's safe browsing feature can detect malicious websites and dangerous downloaded files in real-time. When users attempt to access phishing websites, the browser will pop up a prominent warning page to block access. At the same time, it gives priority to supporting the HTTPS protocol and by default blocks the loading of HTTP resources on HTTPS pages, avoiding mixed content attacks and reducing the risk of data being eavesdropped on or tampered with during transmission. In addition, enabling the "Use secure DNS resolver" option can effectively prevent DNS hijacking attacks.
Process isolation and sandboxing mechanism: This is one of Chrome's core security strategies. It allocates an independent rendering process to each tab, and all web content runs in a sandboxed environment. For example, if a tab is implanted with malicious code, the code will be restricted to the current process and sandbox, neither affecting other tabs nor being able to break through the restrictions to access the user's local file system. Chrome 142 also introduces the "origin isolation" model, which isolates each "origin" composed of a protocol, domain name, and port into an independent process, further enhancing security.