washing my language.

This commit is contained in:
colin 2023-12-13 17:46:42 +00:00
parent 954e848bd7
commit 08934d9094
1 changed files with 3 additions and 3 deletions

View File

@ -4,11 +4,11 @@
1. **Manufacturer Level**:
- Contains general policies and information applicable to all devices from that manufacturer.
- Includes a `whitelist-ips.json` and `security-contact.json` relevant to the entire range of products.
- Includes a `safelist-ips.json` and `security-contact.json` relevant to the entire range of products.
2. **Device-Specific Level**:
- Provides detailed, device-specific instructions and information.
- Contains its own `whitelist-ips.json`, `security-contact.json`, and `firewall-profile.json`.
- Contains its own `safelist-ips.json`, `security-contact.json`, and `firewall-profile.json`.
- Device-specific information overrides manufacturer-level information when present.
#### Example Structure
@ -27,7 +27,7 @@
#### Precedence Rules
- **Device-Specific Over Manufacturer-Level**: Routers and other network management tools should prioritize device-specific instructions and settings. If a device-specific `whitelist-ips.json` or `security-contact.json` exists, it should override the manufacturer-level files.
- **Device-Specific Over Manufacturer-Level**: Routers and other network management tools should prioritize device-specific instructions and settings. If a device-specific `safelist-ips.json` or `security-contact.json` exists, it should override the manufacturer-level files.
#### Goals for Hierarchical Safelist and Contacts