chore: add SECURITY.md and Apache-2.0 LICENSE

Author: mak3r-cyber

LICENSE

@@ -1,27 +1 @@
-# CODEOWNERS
-* @mak3r-cyber
-
-# SECURITY.md
-Security contact: security.contact@mak3r-cyber.dev
-
-# LICENSE File
-MIT License
-
-Copyright (c) 2025 Kamilia Meliani / Lazreg Meliani
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Apache License 2.0

SECURITY.md

@@ -1,27 +1,5 @@
 # Security Policy
-
-## Reporting a Vulnerability
-
-We take the security of our framework seriously and appreciate the community's efforts to responsibly disclose vulnerabilities.
-
-If you believe you have found a security vulnerability in the Healthcare IoMT Risk Assessment Framework, please follow these guidelines:
-
-1. **DO NOT** open a public GitHub issue.
-2. **DO NOT** discuss the vulnerability publicly until it has been patched.
-3. **REPORT PRIVATELY:** Send an email to the project maintainer at:
-   **[VOTRE_EMAIL_DE_SECURITE]**
-4. **Encryption:** If possible, use the project maintainer's PGP key (available upon request) to encrypt the report.
-
-### Information to Include in the Report
-
-Please include the following details to help us assess the vulnerability quickly:
-* A clear description of the vulnerability (type, impact).
-* The exact component or file affected (e.g., `tools/csv2xlsx.py`).
-* Steps to reproduce the vulnerability (proof of concept).
-* Any suggested mitigation or fix.
-
-## Our Policy
-
-We aim to acknowledge all private reports within **3 business days** and plan a full response or patch within **30 days** depending on the severity.
-
-Thank you for helping keep this project secure.
+Signalement vulnérabilités: security.contact@mak3r-cyber.dev
+Délai de divulgation responsable: 90 jours (par défaut).
+Branches supportées: main.
+Pas de données réelles dans les issues.