> ## Documentation Index
> Fetch the complete documentation index at: https://docs.near.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Learn about smart contract security best practices on NEAR, including common vulnerabilities, attack vectors, and how to build secure decentralized applications.

Here you will find information on how to keep your smart contract and decentralized applications secure.

<Tip>
  Please take some time to go through this section, it will help you to keep your dApp safe
</Tip>

***

## 🐞 Bug Bounty Program

NEAR has a [bug bounty program](https://hackenproof.com/company/near/programs) . Please use it if you find any security errors in the protocol, core contracts or web. Hackers - help audit, test, and toughen NEAR up!

## ✅ Security Checklist

Make sure to keep your smart contract safe by running through our [security checklist](./checklist).

## 🛡️ Security Concepts

Learn important security concepts to keep your dApp safe and sound.  Read about:

* Keeping [callbacks safe](./callbacks)
* Understanding [frontrunning](./frontrunning)
* Understanding [sybil attacks](./sybil)
* Understanding [reentrancy attacks](./reentrancy)
* Making sure the owner of an account is [the one calling](./one_yocto)
* Understanding the complexity of [generating random numbers](./random)
* Protecting from a [small deposit attacks](./storage) draining your account

## 🎞️ External Resources

An awesome video series on Smart Contract Security by [https://twitter.com/timurguvenkaya](https://twitter.com/timurguvenkaya) can be found on YouTube:

<iframe width="100%" height="315" src="https://www.youtube.com/embed/DrRr6nru0no?si=FxLJK-LYHrAqX0hc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen />