# Security
The #1 priority for Atlas Protocol is the security of users' assets. This is achieved through a carefully crafted array of security measures outlined below.
### Security Audit (Under Review)
We're currently undergoing a security audit by Halborn, a leading blockchain security firm. This audit will thoroughly examine the protocol's smart contracts, architecture, and overall security posture.
### Native vs. Wrapped or Bridged BTC
By utilizing **native** Bitcoin staking instead of wrapped or bridged BTC, Atlas Protocol significantly reduces potential attack vectors associated with cross-chain bridges and centralized custodians.
### Real-time Protocol Monitoring
Atlas employs both internal and external advanced monitoring systems to track the protocol's operations in real-time, allowing for quick detection and response to any anomalies or potential security threats. We have engaged a third party, 24/7 security monitoring firm and also built our own network of validator nodes to validate transactions, including block-by-block proof of reserves.
### Secure MPC Infrastructure
Leveraging NEAR's Multi-Party Computation (MPC) nodes enhances the security of cross-chain operations and key management, providing an additional layer of protection for user assets.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.atlasprotocol.net/atlas-protocol-basics/security.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.