How Meta works with the security sector to secure the internet


 Bug hunting is challenging and even goes unnoticed in our sector. Every engineering business must undertake the undervalued but crucial task of developing scalable issue detection tools across huge codebases and open source frameworks. Some of our industry's best work is frequently undiscovered since the ideal result is that defects be spotted and addressed before they are exploited.

But information sharing about bugs found by our engineers or bug bounty researchers has inspired fresh concepts and led to inventive solutions to boost the platform's security. We think that regularly disclosing our most important lessons to the outside world will help our industry advance and be more transparent.

We're pleased to announce the release of the first in a series of regular Bug Bulletins, in which we'll discuss some of the noteworthy discoveries found in both our own and outside code. In addition to providing updates on pertinent security initiatives, we'll utilise these bulletins to give overviews of specific problems as well as occasionally thorough dives into them.

How Meta checks for bugs

Here is some background information on how we at Meta seek for security flaws before we get into the most recent discoveries: A crucial component of our "defense-in-depth" security strategy is finding and repairing flaws. By using this strategy, we have added additional levels of security to our platform. We have additional layers of protection in case a flaw in our code gets past one line of defence.

It's almost difficult to produce error-free code, therefore both proprietary and open source software frequently has flaws. Like our competitors, we have a dual strategy. While we're continuously working to make our code better before it enters production, we also incorporate layers of security to help avoid and find vulnerabilities in existing code as soon as feasible. To keep our community safe, we use a combination of automated tools, security reviews, red teaming, and our Bug Bounty programme. This work isn't carried out in a silo or by a single crew. Additionally, issues found in one area of the product frequently influence how we approach our work in a completely unrelated section of the codebase.

Work on static and dynamic analysis

Our developers have more time to focus on analysing more complicated scenarios thanks to the automated static analysis tools that let us review vast amounts of code at scale. Our in-house technologies have been developed over the last five years, and after constant improvement, they now aid in the discovery of around 70% of the security flaws we detect. For instance, this year, our work on Zoncolan, which examines Hack code, has assisted us in finding more than 1,300 flaws.

Work by Red Team X

In addition to looking for bugs in our own code, Red Team X also keeps the rest of the internet secure by identifying security flaws in third-party hardware and software. We routinely notify businesses of flaws in third-party code as part of our responsible disclosure policy, and we work closely with them to test and validate their mitigations. Here are a few recent instances of intriguing industry-wide partnerships we've had.

In order to harden a line of eNodeBs, the wireless access points that offer cell service to phones and other LTE devices and enable them to connect to the network, we also collaborated with Airspan, a provider of hardware and software for 4G and 5G networks. We identified problems and validated the patches for vulnerabilities that may have given networked and local adversaries access to the root command execution. An attacker may have decreased availability by turning off cell service if they had taken over the "last hop" of the LTE infrastructure. According to the results of our analysis, an attacker may have accessed the encrypted user traffic but couldn't have decrypted it.

Bug bounty programmes

One advantage of running a Bug Bounty programme for more than ten years is that some of our researchers have spent years hunting on our platform and have grown very accustomed to our goods and services. These researchers are able to look past the obvious problems and aid in the discovery of important but uncommon bugs that the general public might not be aware of.

We appreciate any comments from our industry colleagues and partners as we continue to develop the style of these Bug Bulletin updates, and we sincerely hope that they would let us know what they would find most useful to read about next on the Engineering at Meta blog.


Comments