Security & Audits
Aave has been implemented with security as priority. The system has been designed to be safe and secure, and all the necessary resources are spent in order to ensure that the protocol matches the highest security standards.
Below are the links to all audit reports and formal verification for Aave V3.0.1
V3.0.1 Audits
V3 Audits
Client Application Security
Aave Interface follows the best practices to ensure a safe interface to interact with the protocol. Here are some protective measure that are taken.
DDOS Protection: Advanced cloud-based DDoS protection services are used to identify and neutralize threats before they reach interface infrastructure. Scalable solutions ensure applications remains accessible, even during periods of high request volume.
DNS Steps to Protect the Domain: To safeguard the domain, DNSSEC is used to protect against DNS spoofing and ensure domain name requests are securely authenticated. Regular monitoring and updates to DNS configurations help prevent unauthorized domain transfers.
Intrusion Detection: The front-end employs state-of-the-art intrusion detection systems (IDS) that monitor for suspicious activities and potential threats, ensuring immediate detection and response to protect user data.
Unwanted Front-End Modification Detection: Content Security Policy (CSP) and Subresource Integrity (SRI) checks are used to detect and prevent unauthorized modifications to front-end code, maintaining the integrity and security of the application.
IPFS Naming Records: Each commit of the Aave Interface codebase is automatically deployed to IPFS. The app.aave.com IPNS pointer and domain text records, using the DNSLink standard, are continuously updated to reflect latest deployment hash.
Last updated