> For the complete documentation index, see [llms.txt](https://metaversus.gitbook.io/metaversus-ecosystem-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metaversus.gitbook.io/metaversus-ecosystem-overview/technologies/bsc/security.md).

# Security

The BSC ecosystem consists of multiple parts and participants and each comes with a different set of threats. There’s code and the algorithm, validators and their hardware, projects building on BSC, and also the individuals using it.

The decentralized BSC blockchain is running on an open-source code accessible to third parties and the public for auditing. With open-source code, anyone (with required technical knowledge) has the ability to review the code line by line and assess the possible weakness and threats. The PoSA algorithm built around 21 elected validators prevents individual validators from gaining too much control over the network and going rogue.

**The BSC network and the algorithm it operates on are indeed very safe**. The track record of BSC is clean of incidents or hacks showing that there are no known vulnerabilities or attack vectors that could be abused on the blockchain itself. Security teams and projects incentivized by the bounty program rigorously test every element of BSC’s security on a regular basis, ensuring that even the slightest issues get resolved immediately.\
\
We will also look at areas such as but not limited to:\
\
Malware detection, Spyware, DDOS attacks, Insider threats, Cross-site scripting, Man in middle attacks (MitM)\
Zero-Day Exploits, Blockchain Contract Audits, Blockchain Security Audits, Governance Jousting, botting, token sniping, whaling.\*