If you are using V3 in a network environment where direct access to AhnLab servers is not available, such as an internal network or an isolated (air-gapped) network, you can update V3 using one of the following methods:

• Allow V3 update servers through the firewall
• Use a management server such as EPP
• Perform manual updates using engine files

Allowing V3 Update Servers Through the Firewall

If you allow V3 update servers through your firewall, product authentication and automatic updates can be performed normally.

Information about V3 update servers and ports is provided through the CDN list. For instructions on how to request the CDN list, please refer to the document below.

• Requesting AhnLab Server IP List Documentation

Updating V3 Through a Management Server

If you are using a management server such as EPP, you can update V3 through EPP.

If the EPP server is also located in an isolated network and cannot perform automatic updates, please refer to the FAQ below for instructions on manually updating the EPP engine files.

• [EPPM] How to Upload Engine File to the EPP Management in an offline environment.

Manually Updating V3 Using Engine Files

If you are not using EPP and cannot allow access to the update servers through the firewall, you can update V3 using engine files and patch files after completing offline product authentication.

For detailed instructions, please refer to the documents below.

• [V3] V3 Offline Product Verification Method
  • If you are still using a legacy product number consisting of 18 digits, offline authentication is not required.