Core Principles of Chromium team Security Development

Google's Chromium browser security rewards program will surely be fresh in your memory. People who have discovered and successfully fixed vulnerabilities will be rewarded with a total of $1 million for reward expenses. Would you like to see how Chromium's development team thinks about security issues?

Don't jump out of your way

To ensure user security, you need to carefully balance the availability, performance, and security of the product. If we implement well, all of these factors should be closely linked and all of them are almost transparent to users. We use transparent Automatic Updates to avoid too many upgrade prompts, and avoid pop-up dialog box prompts. These will only allow qualified users to ignore security prompts. When a security prompt is necessary, make sure that the prompt content is clear and only the most important information is displayed, such as the user name and SSL status in the address bar.

In-depth defense architecture design must be more in-depth)

We designed Chrome's security architecture to achieve hierarchical defense and avoid spof. Chrome's sandbox architecture represents one of the most effective parts of this strategy, but it is far from the complete architecture. We have also adopted the best anti-attack technologies, including ASLR, DEP, JIT hardening, and SafeSEH, and our customized technologies in Chrome OS project include Safe Browsing, out-of-date plugin blocking, silent auto-update, and verified boot. We will continue our research efforts and advance the research results on sandbox and control flow integrity.

Security is the responsibility of the entire team.

There is a common misunderstanding that security is only a feature of the product or a component that can be added. In fact, the security of any complex software product is a cross-domain issue, which is determined by millions of seemingly harmless decisions that are made every day in the minds of developers. This is why it is important for every member of the development team to pay attention to the security development practices and work together with the security team throughout the project's lifecycle. Developers' common awareness of security development helps us complete auditing and regression testing during normal security reviews.

Speed determines everything

The security of a user depends on the quick response to and resolution of security vulnerability issues, whether found in an internal test or reported by a third party. We are committed to solving all security issues and providing them to our users through the fast automatic update mechanism. This approach allows us to stay ahead of the industry in response to security defects. Even when dealing with a complicated and politically colored problem, although we are not the source of content release, but we still try our best to solve this problem. This is the legendary content review and filtering mechanism ).

Transparent Processing

We will not reduce the impact of security issues, or bury defects through silent upgrades, because this is poor for the user experience. On the contrary, we provide users and administrators with the information they need to accurately locate and assess risks. We have made public our security issue handling procedure documents, about Chrome and defects reports dependent on Chrome components, all repaired items have been closed-whether they are detected internally or reported externally. Whenever possible, we will list all security issues that have been fixed in the release note, and disclose the underlying details, as long as other affected projects have enough time to deal with them.

Embrace the community

No software product is perfect, and even with the best development and review processes, bugs will still become the fish of the Internet. That is why we pay the highest respect for the contributions made by independent security research organizations and communities that help us find and address Software defects. In return, we will do our best to express our gratitude for their contributions by reporting, giving bonuses, and sponsoring Security seminars. We make full use of community support and do our best to expand the community to a greater extent. We can directly hire programmers in the community to join our team and maintain partnerships with independent security consultants, which are industry leaders.

Making the Internet safer for everyone

Security is not a game. If a Browser fails to be successful on security issues, the rest will be useless. When the best security technology can be used by everyone, we will become better. To achieve this goal, we work closely with standards-making organizations and other browser vendors to promote our cooperation on multiple standards, including public key pinning, Content Security Policies, and SPDY. We also open-source technology or make our security technology widely available. For example, Native Client/Pepper, Open Type Sanitizer, application sandboxing, and Safe Browsing ).

Original article address