diff --git a/certifications/additional_materials_for_certs/detecting_honeypots_and_sandboxes.md b/certifications/additional_materials_for_certs/detecting_honeypots_and_sandboxes.md
new file mode 100644
index 0000000..12b2d87
--- /dev/null
+++ b/certifications/additional_materials_for_certs/detecting_honeypots_and_sandboxes.md
@@ -0,0 +1,33 @@
+## Techniques for Detecting Honeypots
+
+1. **Network Behavior Analysis**:
+   - **Unusual Traffic Patterns**: Honeypots may generate unusual traffic patterns or responses. Monitoring for anomalies in network traffic can help identify such systems.
+   - **Fake Services**: Some honeypots run services that may have tell-tale signs of being fake, such as outdated software versions or uncommon service responses.
+
+2. **System Fingerprinting**:
+   - **OS and Service Fingerprinting**: Using tools like **Nmap** or **Netcat**, attackers can probe systems to identify discrepancies in OS versions or service configurations that might indicate a honeypot.
+   - **Known Signatures**: Some honeypots have identifiable signatures or configurations. Comparing system responses against known signatures can help in detection.
+
+3. **Interaction Analysis**:
+   - **Response Patterns**: Honeypots often have scripted or automated responses. Analyzing the nature and timing of responses can reveal if the system is a honeypot.
+   - **Behavioral Analysis**: Observing how the system behaves under different conditions. Honeypots might not handle edge cases or unusual commands as well as a real system would.
+
+4. **Honeypot-Specific Tools**:
+   - **Honeypot Detection Tools**: Tools like **Honeyd Detector** or **Honeypot Hunter** can help in identifying honeypots by analyzing network traffic and system responses.
+
+## Techniques for Detecting Sandboxes
+
+1. **System and Environment Checks**:
+   - **File System Analysis**: Sandboxes may have distinct file system structures or paths. Malware can check for specific directories or files commonly associated with sandbox environments.
+   - **Process and System Calls**: Analyzing running processes and system calls can reveal sandbox-specific behaviors or configurations.
+
+2. **Timing and Behavior Analysis**:
+   - **Delay Tactics**: Some sandboxes have time-based triggers or delays before executing certain actions. Malware can use timing analysis to detect these behaviors.
+   - **Resource Constraints**: Sandboxes may have constrained resources or limited functionality. Observing resource usage and system performance can help identify sandboxes.
+
+3. **Anti-Sandbox Techniques**:
+   - **Anti-Debugging**: Malware can use anti-debugging techniques to detect if it is being analyzed in a sandbox environment. This includes checking for debugger processes or specific debugging tools.
+   - **Environment Checks**: Malware can perform checks for known sandbox environments, such as virtual machine artifacts or specific registry keys in Windows-based sandboxes.
+
+4. **Sandbox Detection Tools**:
+   - **Sandbox Detection Tools**: Tools like **Cuckoo Sandbox** or **Any.Run** can be used to analyze behavior and detect if the system is running in a sandbox environment.