From 72e3527d6c9d3ca2e4f7856d1cc373d6ff13d96f Mon Sep 17 00:00:00 2001
From: colin <colin@noreply@nixc.us>
Date: Wed, 13 Dec 2023 18:35:19 +0000
Subject: [PATCH] Update firewall-profile.md

---
 firewall-profile.md | 65 ++++++++++++++++++++++++++++++++++++++-------
 1 file changed, 56 insertions(+), 9 deletions(-)

diff --git a/firewall-profile.md b/firewall-profile.md
index 47a81b2..10cfb14 100644
--- a/firewall-profile.md
+++ b/firewall-profile.md
@@ -1,4 +1,4 @@
-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.
+Incorporating a directionality feature into the `firewall-profile.json` to specify the traffic direction for each rule is crucial 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 necessary. Let's revise the example with this requirement in mind.
 
 ### Revised `firewall-profile.json` with Directionality
 
@@ -31,21 +31,68 @@ Incorporating a directionality feature into the `firewall-profile.json` to speci
   ]
 }
 ```
+#### Modes depicted in these diagrams.
 
-#### Explanation:
+##### Outbound rules
+```mermaid
+graph LR
+    A[Internet/External Network] -->|Inbound Rule| B(Firewall)
+    B -->|Outbound Rule| C[Internal Network/Device]
+    style B fill:#f9f,stroke:#333,stroke-width:2px
+```
+##### In this diagram:
 
-- 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.
+    A represents the Internet or an external network.
+    B is the Firewall, which applies different rules based on the direction of traffic.
+    Inbound Rule: Traffic coming from the Internet (A) to the internal network/device (C) passes through an inbound rule at the Firewall (B).
+    Outbound Rule: Traffic originating from the internal network/device (C) and going out to the Internet (A) is governed by an outbound rule at the Firewall (B).
 
+##### Inbound Rules
+```mermaid
+graph LR
+    A[Internet/External Network] -->|Inbound Rule| B(Firewall)
+    B --> C[Internal Network/Device]
+    style B fill:#f9f,stroke:#333,stroke-width:2px
+```
+**Explanation**:
+- **A** represents the Internet or an external network.
+- **B** is the Firewall applying inbound rules.
+- **Inbound Rule**: Traffic from the Internet (A) to the internal network/device (C) is filtered by the inbound rule at the Firewall (B).
+
+##### Both Directions Rules
+```mermaid
+graph LR
+    A[Internet/External Network] -->|Inbound Rule| B(Firewall) -->|Outbound Rule| A
+    C[Internal Network/Device] -->|Outbound Rule| B -->|Inbound Rule| C
+    style B fill:#f9f,stroke:#333,stroke-width:2px
+```
+**Explanation**:
+- **B** is the Firewall managing both inbound and outbound traffic.
+- **Inbound Rule**: The inbound rule controls traffic from the Internet (A) to the internal network (C).
+- **Outbound Rule**: Traffic from the internal network (C) to the Internet (A) is governed by the outbound rule.
+- Arrows indicate bidirectional flow, representing "BOTH" direction rules.
+
+##### Internal (Intra-Network) Rules
+```mermaid
+graph LR
+    C1[Device 1] -->|Internal Rule| C2[Firewall/Router]
+    C2 -->|Internal Rule| C3[Device 3]
+    C1 -. "No direct access" .- C3
+    style C1 fill:#ff9,stroke:#333,stroke-width:1px
+    style C2 fill:#9f9,stroke:#333,stroke-width:1px
+    style C3 fill:#99f,stroke:#333,stroke-width:1px
+```
+**Explanation**:
+- **B** is the Firewall implementing internal network rules.
+- **Internal Rule**: Controls traffic between devices within the internal network (e.g., Device 1, Device 2, Device 3), ensuring that they only communicate as per defined policies.
+
+---
 ### 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.
+- **Precision in Rule Application**: Directionality helps apply 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.
+- **Avoiding Unrestricted Access**: By making directionality a required feature, the architecture reinforces that no device should have unrestricted open access unless it's essential for its function.
 
 ---