diff --git a/firewall-profile.md b/firewall-profile.md
new file mode 100644
index 0000000..47a81b2
--- /dev/null
+++ b/firewall-profile.md
@@ -0,0 +1,92 @@
+Incorporating a directionality feature into the `firewall-profile.json` to specify the traffic direction for each rule is a crucial aspect for enhancing network security. This addition ensures that each rule clearly defines whether it applies to inbound or outbound traffic, helping to prevent unrestricted open access unless absolutely necessary. Let's revise the example with this requirement in mind.
+
+### Revised `firewall-profile.json` with Directionality
+
+#### Structure:
+
+```json
+{
+  "firewall_rules": [
+    {
+      "rule": "ALLOW",
+      "direction": "INBOUND",
+      "port": 443,
+      "protocol": "TCP",
+      "description": "Allow inbound HTTPS traffic for secure web communication."
+    },
+    {
+      "rule": "BLOCK",
+      "direction": "INBOUND",
+      "port": 23,
+      "protocol": "TCP",
+      "description": "Block inbound Telnet access to prevent insecure control access."
+    },
+    {
+      "rule": "ALLOW",
+      "direction": "OUTBOUND",
+      "port": 53,
+      "protocol": "UDP",
+      "description": "Allow outbound DNS queries."
+    }
+  ]
+}
+```
+
+#### Explanation:
+
+- Each firewall rule is an object within the `firewall_rules` array.
+- `rule` indicates the action (ALLOW/BLOCK).
+- `direction` specifies whether the rule is for `INBOUND` or `OUTBOUND` traffic, clearly defining the traffic flow.
+- `port` and `protocol` detail the specific network port and protocol to which the rule applies.
+- `description` explains the purpose and necessity of each rule, aiding in understanding and compliance.
+
+### Importance of Directionality in Firewall Rules
+
+- **Enhanced Security**: Clearly defined directional rules ensure that devices don't inadvertently allow unsafe inbound or outbound connections.
+- **Precision in Rule Application**: Directionality helps in applying firewall rules more precisely, depending on the nature of the device and its network interactions.
+- **Compliance with Best Practices**: Requiring directionality in firewall rules aligns with industry best practices for network security, ensuring devices are safeguarded against unauthorized access.
+- **Avoiding Unrestricted Access**: By making directionality a required feature, the architecture reinforces the principle that no device should have unrestricted open access unless it's essential for its function.
+
+---
+
+### Safelist-Based Intra-Network Firewall Rules
+
+#### `firewall-profile.json` Structure for Device-Level Rules
+
+```json
+{
+  "intra_network_rules": [
+    {
+      "rule": "ALLOW",
+      "direction": "INTRA-NETWORK",
+      "port": 80,
+      "protocol": "TCP",
+      "description": "Allow HTTP traffic within the network for device management interfaces."
+    },
+    {
+      "rule": "ALLOW",
+      "direction": "INTRA-NETWORK",
+      "port": 53,
+      "protocol": "UDP",
+      "description": "Allow DNS queries within the network for domain resolution."
+    }
+    // Additional specific allow rules as necessary
+  ],
+  "default_rule": "BLOCK"
+}
+```
+
+#### Explanation
+
+- **Safelist Rules**: The `intra_network_rules` array contains specific rules that explicitly allow certain types of traffic within the network.
+- **Direction**: `"INTRA-NETWORK"` specifies that these rules apply to traffic within the local network.
+- **Default Rule**: The `"default_rule": "BLOCK"` at the end enforces that any traffic not explicitly allowed by the earlier rules should be blocked. This default-deny stance is a vital principle of a Safelist approach.
+- **Rule Justification**: Each rule includes a `description` explaining why the particular type of traffic is necessary for the device's operation.
+
+### Importance of Whitelist Approach
+
+- **Enhanced Security**: A Safelist approach significantly reduces the attack surface by default to deny all but explicitly allowed traffic.
+- **Minimizing Unnecessary Access**: By specifying only the necessary traffic types, devices are prevented from accessing or being accessed by other network resources that are irrelevant to their function.
+- **Preventing Lateral Movement**: This method is particularly effective in containing potential security breaches by limiting the ability of an attacker to move laterally within the network.
+
+Applying a safelist methodology to intra-network firewall rules, especially in the context of IoT and smart devices, provides a robust framework for ensuring that devices operate securely and interact with the network only as intended.
\ No newline at end of file