diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..9941b7e
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,51 @@
+# Security Policy
+
+## Vulnerability Disclosure Policy
+
+At SoroTask, we take the security of our decentralized task marketplace seriously. If you believe you’ve found a security vulnerability in SoroTask, please let us know right away.
+
+### Reporting a Vulnerability
+
+**Do not report security vulnerabilities via public GitHub issues.**
+
+Please report any identified vulnerabilities by emailing `security@sorolabs.org`.
+
+Your report should include:
+
+- A description of the vulnerability.
+- Steps to reproduce (PoC).
+- Potential impact.
+- Any suggested fixes (if available).
+
+### Scope
+
+The following components are in scope for this policy:
+
+#### Primary Scope (On-chain)
+
+- **Smart Contracts**: All code in `/contract` deployed on Soroban.
+- **Protocol Logic**: Any issues related to reward distribution, task execution integrity, or core protocol mechanics.
+
+#### Secondary Scope (Infrastructure & Frontend)
+
+- **Official Keeper Service**: The execution logic in `/keeper` (e.g., DoS, memory leaks, or execution failures).
+- **Official Frontend Dashboard**: The user interface in `/frontend` (e.g., XSS, UI manipulation, or phish-prone components).
+
+### Prohibited Actions
+
+- Any testing that interferes with other users' tasks or funds.
+- Denial of Service (DoS) attacks.
+- Social engineering or physical security attacks.
+- Publicly disclosing the vulnerability before we have had a chance to fix it.
+
+### Our Commitment
+
+We will acknowledge your report within **48 hours** and provide a timeline for resolution based on the severity of the issue.
+
+- **Acknowledgment**: Within 2 working days.
+- **Initial Evaluation**: Within 5 working days.
+- **Resolution**: Dependent on severity (aiming for < 30 days).
+
+---
+
+_Safe Harbor: If you conduct your security research activities within this policy, we will not initiate legal action against you._