How to allow antivirus updates on an isolated corporate network without enabling general internet access
Use defined sources, vendor update destinations, required ports, controlled DNS recursion, time synchronization, logging, and default deny to create auditable least-privilege egress.

Establish a factual baseline with “update-server and endpoint source addresses” and “vendor update FQDNs and CDN changes”, then move to “DNS resolution path”. Use routing, policy, session state and real application traffic as the evidence chain and avoid changing production before the fault boundary is clear.
Risk boundaries and prerequisites
Start by checking update-server and endpoint source addresses, vendor update FQDNs and CDN changes and DNS resolution path independently. A healthy result for one of these checks does not establish the state of the entire service path.
Evidence and safe checks
| Check | Why it matters | Recommended action |
|---|---|---|
| 01 · update-server and endpoint source addresses | Checking update-server and endpoint source addresses helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of update-server and endpoint source addresses. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 02 · vendor update FQDNs and CDN changes | Checking vendor update FQDNs and CDN changes helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of vendor update FQDNs and CDN changes. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 03 · DNS resolution path | Checking DNS resolution path helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of DNS resolution path. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 04 · required outbound TCP 80/443 | Checking required outbound TCP 80/443 helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of required outbound TCP 80/443. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 05 · default deny and hit logging | Checking default deny and hit logging helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of default deny and hit logging. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
| 06 · failure rollback and antivirus-definition version validation | Checking failure rollback and antivirus-definition version validation helps establish whether the complete request, response and return path matches the intended policy; compare it with a known-good baseline and the incident timeline. | Record the actual state of failure rollback and antivirus-definition version validation. Record VLAN, routes, firewall hits and DNS results and gather relevant logs using non-disruptive tests first. |
Investigation and change sequence
- Capture a baseline for update-server and endpoint source addresses and vendor update FQDNs and CDN changes and compare it with a known-good system.
- Correlate evidence from DNS resolution path and required outbound TCP 80/443 to distinguish the direct fault from dependent symptoms.
- Only if evidence points to default deny and hit logging, plan a controlled change with backups, a change window and rollback triggers.
- Finally check failure rollback and antivirus-definition version validation and the real business workflow. Verify end-to-end business access, return routing and error logs, with a defined rollback check.
Validation and rollback evidence
- Verify end-to-end business access, return routing and error logs, with a defined rollback check.
- Recheck default deny and hit logging and failure rollback and antivirus-definition version validation against the expected business outcome.
- Retain initial configuration, event evidence, validation results and rollback triggers for production changes.
Common actions that increase risk
- Assuming update-server and endpoint source addresses is sufficient while overlooking vendor update FQDNs and CDN changes and dependent checks.
- Changing several settings before preserving the original evidence for DNS resolution path.
- A successful port probe is not proof of application functionality; do not broaden access rules blindly.
Common questions and acceptance criteria
What should be checked first?
Begin with update-server and endpoint source addresses and vendor update FQDNs and CDN changes. Capture reproducible errors and protect recoverable data before changing production.
What proves the issue is resolved?
Verify end-to-end business access, return routing and error logs, with a defined rollback check.
What evidence should be retained?
Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.
