Security rules

This is a list of the security policies Chromium has published.

• Rule of Two - don't handle untrustworthy data in the browser process in an unsafe language
• The browser process should not handle messages from web content
• Behavior should be part of Chrome's binaries or delivered via component updater rather than delivered dynamically
• Rules for Android IPC
• Always assume a compromised renderer
• Use origin not URL for security decisions
• Controlling access to powerful web platform features
• Security considerations for browser UI
• Guidelines for URL display
• Avoid adding cross-origin full-page overlays
• Security Guidelines for LLMs and other large models in Chrome
• Windows HANDLE handling

You can also find our position on various matters in the security FAQ: for example, on local attackers or on the privilege accorded to enterprise admins.