FAQs – Advanced

Prev Next

Product FAQs for TXOne Network Defense Solutions: Edge Series



This document collects and answers the most common questions about our line of TXOne Network Defense products known as the Edge Series. Possible categories include, but are not limited to, Deployment, Maintenance, Security, License, etc.

License

1. What is the system behavior when there is no ODC-VA / EdgeOne-Node license?
Connections between ODC-VA / EdgeOne and devices will be closed.

2. What is the system behavior when there is no Edge series software license?
ODC-VA / EdgeOne will not dispatch updates to EdgeIPS devices.

3. What is the system behavior when the ODC-VA / EdgeOne-Node software license has expired?
Connections between ODC-VA / EdgeOne and devices will be closed.

4. What is the system behavior when the Edge series software license has expired?
ODC-VA / EdgeOne will not dispatch updates to EdgeIPS devices.

5. What is the system behavior when the number of managed nodes with a Trend Micro Activation Code & TXOne License Key exceeds the seat count of the ODC-VA / EdgeOne-Node license?
New nodes (EdgeIPS/IEF devices) will not be able to register with the ODC-VA / EdgeOne license.

6. What is the system behavior when the number of managed EdgeIPS devices exceeds the seat count of the Edge series software license?
ODC-VA / EdgeOne will not dispatch updates to EdgeIPS devices.

7. What is the system behavior when the number of managed nodes exceeds the seat count of the ODC-VA / EdgeOne-Node software license?
This can happen when users reduce the number of nodes while renewing their license. ODC-VA / EdgeOne will remove the extra nodes so that the number of total managed nodes equals to the seat count of the license. (Starting from offline devices, then the latest connected devices)

8. Can users reduce the seat count when renewing ODC-VA / EdgeOne-Node or Edge series software licenses?
Yes, but you need to check with the TXOne OM team and go through the business process.

9. How does ODC-VA / EdgeOne retrieve the latest license content?
ODC-VA / EdgeOne will do an entitlement check every time users clicks the “Refresh” button, or when a license expires.

10. Can users activate licenses when ODC-VA / EdgeOne has no internet access?
A future release (after GM) will allow users to import license files.

11. Does ODC-VA / EdgeOne-VA / EdgeOne support offline license activation for the Trend Micro Activation Code & TXOne License Key?
Starting from v1.1, ODC-VA / EdgeOne-VA will support offline license activation.

AVM (Asset Vulnerability Management)

1. Do I need to upgrade the Edge device firmware to use AVM?
No. AVM is supported so long as EdgeOne runs firmware v2.5+ and Edge devices run v2.0+.

2. What improvements will AVM have if I upgrade the Edge device firmware?
Newer firmware improves device information and OS recognition accuracy, enhancing AVM’s detection capability.

3. Which operating systems are supported for vulnerability detection?
AVM supports Windows and Linux. Embedded system support is planned for Q1 2026.

4. How is AVM different from other vulnerability detection vendor solutions?
AVM integrates vulnerability detection with Virtual Patching and actionable recommendations for end-to-end protection.

5. How long is the AVM trial period?
Edge customers receive a 60-day trial.

6. Does AVM support air-gapped environments?
Yes. Users may manually download AVM pattern updates from MyTXOne Portal.

7. How often are AVM vulnerability patterns updated?
Every two weeks, with out-of-cycle patterns being released as needed.

8. How frequently does AVM process vulnerability data sources?
Data sources are refreshed and processed daily.

9. Can AVM be purchased for a specific number of devices?
No. AVM operates at a network‑wide level and must match the number of management seats.

10. Is there a limit to the number of assets AVM can detect?
No. Coverage depends on your Edge deployment. All visible network assets are detected.

11. What mechanism does AVM use for vulnerability detection?
AVM uses network-based detection, offering real-time visibility.

12. Why do customers need AVM?
AVM strengthens Edge with deeper visibility, vulnerability insights, and actionable protection.

13. Can the AVM license be migrated to another EdgeOne management system?
No. There is only one AVM available for each EdgeOne management system.

Deployment

1. Do Edge devices only support inline deployment? Can they be installed on a switch mirror port for detection only?
EdgeIPS series devices support both inline and offline deployments. Inline deployment allows prevention and monitoring, while offline deployment provides monitoring only. To deploy Edge devices in offline mode, the devices need to connect to mirror ports.

2. What are the steps for deploying Edge devices? How do customers verify the results of the deployment?
- Install EdgeOne and pre-configure its policy settings.
- Configure IP addresses and management settings of Edge devices.
- Physically install Edge devices in the designated field location and connect them to the local network.
- Make sure Edge devices are synced with EdgeOne.
- Check detection logs.

3. What platform is required for installing the CMS? How can it be installed if we don’t have VMware or ESXi?
Currently, EdgeOne supports VMware, Hyper-V, and KVM. If users do not have VMware or ESXi, they can still use Windows-embedded Hyper-V to install EdgeOne.

4. For a PoC, where would TXOne generally recommend Edge devices be placed?
It depends on users’ needs. If an Edge device is placed in front of a critical asset, users can get detailed traffic information, but this information will be limited to that specific asset. If an Edge device is positioned at a higher layer in the network architecture, it will be able to collect more comprehensive asset information, although with less detailed traffic information for each asset.

5. When Edge devices are installed, is it necessary to change our network architecture?
Since EdgeIPS is transparent, there is no need to change the architecture for Edge device installation.

6. We would like to deploy Edge sensors in our virtualized environment. Are virtual appliances supported, and can they be managed centrally?
Yes. Virtual EdgeIPS Pro (02-VA / 04-VA / 08-VA) is supported in firmware v2.3.7, and EdgeOne v2.7 manages them together with physical devices. Virtual appliance support is enabled with the VShell 'va' command, and licenses are shown in the [Virtual Licenses] tab. Ports without a NIC assigned by the hypervisor are displayed as 'Not Assigned'.

7. What platforms are required to install EdgeOne v2.7? We use Nutanix in our data center.
EdgeOne v2.7 supports VMware ESXi 6 or later, VMware Workstation 14 or later, KVM 2.x or later, Hyper-V 10.x or later, and Nutanix AHV 20220304.342 / AOS 6.5.2 LTS or later.

Maintenance

1. How often does TXOne release pattern updates? How can customers obtain a new update?
We regularly release pattern updates every month. If severe vulnerabilities are disclosed, we will also launch out-of-cycle releases within 7 to 10 working days.

2. If customers deploy massive Edge devices, how can they update all the devices within a limited downtime period?
All Edge devices have two partitions for firmware storage. Users can upload new firmware prior to downtime (this will not affect the operation) and apply new firmware during downtime.

3. What backup / restore methods are supported by TXOne Edge devices? What will be preserved in a backup file?
We support a couple of methods to perform backup / restore. The most basic one is to perform them via the device UI. Another way is to leverage the zero-config function restore data via a USB dongle. A backup file includes IP address, policy settings, management settings, and account information.

4. What software update method do Edge devices support? Is an internet connection required?
TXOne Edge devices support both online license update and local license import. If an internet connection is not available, users can still upload updated firmware / pattern files previously obtained from a local computer to the device web console.

5. How can we check and update licenses if we do not have direct internet access for our CMS?
Similar to a software update, EdgeOne (CMS for Edge devices) supports both online license checks and offline activation using a license file. Users can download the license file on any computer with an internet connection and then import the file into EdgeOne for license activation.

6. After a large-scale Edge device deployment, we will have many Edge devices in the field. It will take too much time if we need to log in to each device to change settings. Is there any efficient and convenient approach to solving this issue?
The most straightforward approach is to perform batch configurations through the CMS. In addition, Edge devices support RESTful APIs, allowing you to easily change device configurations and poll data.

7. As the number of Edge devices under EdgeOne management increases, how can we quickly locate a specific Edge device?
In EdgeOne Node Management, users can search specific devices based on their search criteria, such as device names or locations.

8. We have dozens of Edge devices across production lines. During an incident, do we need to log in to each device to enable Emergency Mode?
No. In EdgeOne v2.7, users can select multiple Edge devices across different Edge groups and Edge types, then activate Emergency Mode or restore Normal Mode in a single action. It can be triggered from [Applications] > [Emergencies & Diagnostics], the [Nodes] page, or [Edge Interface Status View]. Please note that devices running firmware earlier than v2.3 show 'Limited Support' and cannot enter Emergency Mode.

9. Policy Rule Auto-Learning generated hundreds of rules, and reviewing them one by one takes too much time. Is there a way to simplify the review?
EdgeIPS Pro v2.3 and EdgeIPS 103/103F v2.3 support Policy Enforcement Rule Aggregation (PEA) and Protocol Filter Profile Aggregation (PFA) to merge learned rules and duplicate profiles. PEA offers a conservative strategy (smaller than Class C) and an aggressive strategy (Class B or C). We recommend starting with the conservative strategy and reviewing the result before applying it. EdgeOne v2.7 also lets users preview the learning result with the applied IPS and Antivirus profiles.

10. We plan to upgrade EdgeOne and all Edge devices to the new versions. What is the recommended order, and what should we pay attention to?
We recommend upgrading EdgeOne to v2.7 first, because v2.7 adds management support for Edge firmware v2.3, and then upgrading the Edge devices (firmware can be uploaded to the standby partition before downtime). After the EdgeOne upgrade, please update the TXOne CVDS Pattern. If you upgrade from EdgeOne v2.0.17, please re-enable ACL after the upgrade. For older Edge firmware, please check the upgrade path in the release notes or contact TXOne support.

11. We do not want to create and maintain local accounts on hundreds of Edge devices just for remote troubleshooting. Is there a better way?
Edge firmware v2.3 supports Direct Remote Access. Once "Allow Direct Remote Access" is enabled on the device, users can access the device from EdgeOne with their EdgeOne account, without creating a local account on each Edge device.

12. What if EdgeOne's disk fills up with logs? How do we prevent EdgeOne from becoming inaccessible?
EdgeOne v2.7.11 fixes the issue where a full disk volume could make EdgeOne inaccessible. In addition, the new VShell 'disk' command lets administrators check disk usage ('disk ls') and reclaim log space from the oldest logs ('disk clean', with a '--dry-run' preview).

13. Accurate time is critical for event correlation. What happens if our NTP server goes down?
EdgeOne v2.7 supports a Secondary NTP Server. If the primary NTP server is unreachable, EdgeOne automatically connects to the secondary server.

14. "We only need to back up specific critical Edge devices in a group. Do we have to back up the whole group?"
No. In EdgeOne v2.7, the periodic backup settings provide a selected device option. Users can select All devices in the group, or Custom to back up only specific Edge devices.

15. "We already have EdgeIPS LE deployed in the field. Can they be managed together with the new firmware versions in EdgeOne v2.7?"
Yes. EdgeOne v2.7 manages EdgeIPS LE v2.1.27 or above and adds support for EdgeIPS LE v2.3, together with EdgeIPS, EdgeIPS Pro and EdgeFire. Please note that new centralized functions such as Emergency Mode require Edge firmware v2.3 or later.

Security

1. Customers usually have multiple different operating systems in OT. Does it matter what systems are installed? Will the OS impact the protection?
TXOne Edge devices inspect and filter network packets to provide protection. As a result, the operating systems protected by these devices do not affect the security performance.

2. If customers have already deployed IT firewalls in the OT environments, why do they still need EdgeIPS devices?
An IT firewall is typically positioned at a higher layer within the network architecture.

3. What are the main differentiators between TXOne solutions and competing solutions from IT firewall vendors?
As TXOne focuses on a wide range of OT verticals, we support more and more OT protocol recognition and controls, including command and function controls. In contrast, competitors can only provide basic protocol-level controls. Additionally, our hardware design is OT-oriented, supporting a wide operating temperature range and a fanless design.

4. We use Splunk in our environment. Can TXOne solutions send detection records to our Splunk servers for integration?
Yes. The Edge CMS EdgeOne supports 3rd-party integration via API and syslog forwarding. EdgeOne can send logs in both CEF and LEEF formats to Splunk servers for integration.

5. What would happen if Edge devices are attacked (e.g., by malicious flooding traffic)?
All Edge devices have built-in self-protection features, including signature-based detection and DoS protection.

6. When gathering asset information, do Edge devices actively scan OT assets and could this cause device failures?
By default, Edge devices will perform passive information collection only and will not send any scan packets to OT assets.

7. If a detected network packet is actually secure, can the detection rule be disabled and the relevant log hidden?
Edge devices support rule-based editing, allowing users to customize actions for each rule, such as disabling it or changing the action to accept or deny.

8. Can Edge devices block our network traffic due to a false positive? If so, how does TXOne address such cases?
Before releasing new signatures, we always conduct internal tests to minimize the occurrence of false positives. However, we can't guarantee with 100% certainty that no false positives will occur. Therefore, we recommend that customers initially set the Edge device rule operation mode to monitoring mode, allowing detection of potential issues without blocking network attacks. Additionally, all Edge devices include a built-in packet capture function, enabling users to download rule-triggering packets for further analysis.

9. Where does TXOne obtain its signatures?
TXOne has its own dedicated pattern team that develops new signatures for comprehensive vulnerability coverage.

10. Is it possible to modify the actions of IPS rules? If patterns are updated, will the previously modified rule actions revert to their defaults?
We support a rule-based editing feature to modify each rule action. The modified action settings will not be affected by pattern updates.

11. We need to comply with SEMI E187. How do TXOne products assist with standard compliance?
As regulated, equipment must support secure protocols for data transmission and to control and limit network port usage. All these requirements can be fulfilled by implementing TXOne Edge solutions.

12."Many of our OT assets run legacy operating systems that cannot be patched. How can we identify these assets and protect them?"
EdgeOne v2.7 shows the OS Type and a Legacy OS tag in Vulnerability View, and the Lifecycle Stage (mainstream or legacy) in Asset View, so users can quickly identify legacy assets. For these assets, Edge devices provide virtual patching through IPS rules, and the VSAR Indicator shows whether IPS coverage is available for each CVE.

13. "Our SOC is introducing AI assistants. Can they query data from EdgeOne? How do we make sure the AI cannot change our settings?"
EdgeOne v2.7 provides a built-in MCP (Model Context Protocol) Service, which allows authorized AI agents to query EdgeOne data such as assets and vulnerabilities without an external server. All MCP tools are read-only, so AI agents cannot change any EdgeOne settings. Access is controlled by a bearer token; generating a new token immediately invalidates the previous one.

14. "After years of operation, our policy rules keep growing. How do we know which rules are actually used and which can be removed?"
EdgeOne v2.7 adds a Hit Count for each Policy Enforcement rule and a Total Hit Count for each rule set. Users can drill down to see which Edge devices and assets matched a rule. The new dashboard widget 'Top Hit Counts by Edge Group' also shows which groups have the most rule hits, helping users clean up unused rules based on evidence.

15. "Our audit requires a login warning banner and stronger authentication for SNMP monitoring. Do TXOne products support these requirements?"
Yes. EdgeOne v2.7 and Edge firmware v2.3 support a configurable Login Message on the login page. SNMPv3 now supports SHA-224, SHA-256, SHA-384 and SHA-512 authentication. Edge firmware v2.3 also adds login protection to strengthen web console security.

16. "We need to align our vulnerability management with EU requirements. Can TXOne IPS rules be mapped to EU vulnerability identifiers?"
Yes. EdgeOne v2.7 and Edge firmware v2.3 support EU Vulnerability Database (EUVD) information in IPS profiles. When EUVD information is available, it is appended to the IPS rule name, so users can map IPS protection to EUVD entries.

Visibility

1. What information can we obtain after installing Edge devices? Is it necessary to connect assets directly to Edge devices for asset information collection?
Edge devices can passively collect asset information, including IP address, MAC address, OS version, and applications in use. Additionally, Edge devices display logs based on configured policy rules, such as cybersecurity logs, protocol logs, and policy violation logs. Direct connections between Edge devices and assets are not required for information collection.

2. If I have multiple assets to protect under different port pairs of a single EdgeIPS Pro, how can I determine which port pair a specific asset is connected to?
Both Edge devices and the CMS allow users to create search filters to locate specific assets based on

3. "We receive too many alerts from IPS, CPSDR and vulnerability detection. How do we decide which ones to handle first?"
EdgeOne v2.7 provides Security Alert View, which consolidates IPS events, CPSDR events and the VSAR Indicator in one place. The VSAR Indicator combines each detected CVE with the exposure of the affected assets and the IPS coverage available, so users can prioritize remediation based on real risk. Users can also switch to [High Severity] to focus on Critical and High alerts only, and drill down to the related rule and asset.

4. "Our asset inventory shows many unknown or inaccurate OS types, especially for embedded devices. Can TXOne improve the asset identification?"
Yes. EdgeIPS Pro v2.3 and EdgeIPS 103/103F v2.3 support the AI Engine Package, which improves OS recognition for Windows, Linux and embedded systems. EdgeOne v2.7 also enhances the vulnerability detection rate for embedded systems. Please note that the AI Engine Package is not listed for EdgeIPS 102 in v2.3.

5. "The system-detected asset information (e.g., OT layer, Internet exposure) does not always match our actual environment. Can we correct it manually?"
Yes. In EdgeOne v2.7, users can override the asset type, OT layer, Internet exposure and lifecycle stage of bookmarked assets. Overridden values are marked as [User Override], and users can filter assets by System Detected or User Override, so it is always clear which values came from the system. Batch editing is also supported.

6. "Our network graph contains thousands of nodes and is difficult to read. How can we quickly find the risky communication?"
EdgeOne v2.7 adds Network Graph filters for Edge type, vulnerable assets, Internet-exposed assets and Edge serial number. The connected node toggle hides nodes without communication, and a breadcrumb trail helps users move back and forth. Users can also jump from OT Layer View or Edge Deployment View directly to the related nodes in the Network Graph.

Networking

1. How many IP addresses do I need to assign during a PoC?
Each Edge device requires one management IP address. EdgeOne also needs one management IP address each.

2. As an intermediate device, what is the throughput capability of an Edge device? What happens if the real throughput exceeds the device limitation?
The throughput ranges from 250 Mbps to 20 Gbps, depending on the model. Smaller models offer lower throughput and are ideal for deployment at lower network layers to provide micro-segmentation for critical assets. In contrast, larger models can be placed at higher layers, such as near a core switch, to inspect east-west network traffic. If the throughput exceeds the device's capacity, packets will be dropped because the CPU cannot handle the incoming traffic. However, the throughput figures in our specifications are based on worst-case scenarios, and customers can typically expect better performance in practice.

3. Which service ports need to be opened?
The most important ports that need to be open are TCP 7590 for management and TCP 443 for web services. For the rest of the ports, please refer to our administrator's guide.

4. What type of interface do Edge devices support? Do Edge devices support fiber connections?
EdgeIPS Pro 1048 / 2096, EdgeIPS Pro 2016F /4016F and EdgeIPS Pro 212-F support fiber interfaces. The rest of the models only support copper interfaces.

5. Does the Edge series have wireless models? How do Edge devices protect wireless assets in OT?
Currently, Edge devices only support wired connections. For wireless asset protection, we recommend placing the Edge devices behind access points.

6. If Edge devices operate in offline mode, will they consume excessive Ethernet switch resources when mirroring network traffic?
Typically, traffic mirroring doesn't consume excessive CPU resources on the switch. If you have concerns about this, we recommend initially limiting traffic mirroring to a few specific ports or VLANs.

7. How does the CMS manage Edge devices? Since direct internet connections for updates are not allowed on the OT network, does the CMS need to use an OT-specific IP address?
Edge devices must proactively initiate connections to EdgeOne, which requires network connectivity. Most Edge devices have MGMT interfaces that connect separately to the IT network for out-of-band management.

8. In OT networks, all network packets are tagged with VLAN IDs. Does TXOne offer a solution to support VLAN?
Yes, both Edge devices and EdgeOne support VLAN-tagged traffic.

9. "We have a communication problem that does not trigger any security event, and TXOne support asks for packet captures. We cannot connect a laptop or configure a mirror port on site. How can we provide the traffic data?"
EdgeIPS Pro v2.3 and EdgeIPS v2.3 support Raw PCAP Recording from the MGMT port and all port pairs. Users can filter by IP address, subnet, TCP/UDP/ICMP port or frame type, and schedule the recording. On physical devices the PCAP files are stored on an external USB drive (on Virtual EdgeIPS Pro, on its local drive), and can be downloaded from the [PCAP File List] page.

10. "Some of our OT applications keep TCP/UDP sessions open but idle for a long time. Can we adjust how long the Edge device keeps these connections?"
Yes. EdgeIPS Pro v2.3 and EdgeIPS v2.3 add TCP and UDP connection timeout settings in the CLI. Please contact TXOne support for the recommended values for your application before changing them.

11. Our EdgeOne is deployed behind NAT, and we used the VShell 'env exip' command to set the external IP. Has anything changed in v2.7?
Yes. The 'env exip' subcommand has been removed in EdgeOne v2.7. Before upgrading a NAT deployment, please contact TXOne support for the recommended configuration. v2.7 also adds the VShell 'dx address' and 'dx traceroute' commands to help verify the connection between Edge devices and EdgeOne.

Operation

1. Will OT network traffic be disrupted if Edge devices experience downtime?
All TXOne EdgeIPS series devices support hardware bypass, which automatically redirects network traffic to guarantee uninterrupted OT operations in the event of an Edge device failure.

2. How long does it take for the bypass mechanism to recover the OT traffic?
In general, the recovery time is within 3 seconds, depending on the connected uplink/downlink devices.

3. How long will the network be disconnected during the solution installation?
We recommend completing pre-configuration before physically installing Edge devices. During deployment, the network will experience a brief disconnection (less than 1 minute) because the Ethernet cable will be unplugged and then re-plugged.

4. What can we do if we don’t want any traffic blocking during the PoC?
Edge devices support monitoring mode for detection only, without blocking any network traffic.

5. If Edge devices cause a disconnection, is there a way to quickly enable bypass mode to allow traffic to pass through and recover our traffic?
For debugging purposes, Edge devices support a force-open bypass feature that directly enables bypass capability. When this mode is activated, traffic will pass through without any inspections.

6. Will inspection cause any latency? If so, how much? Will our operations be affected?
Based on our internal tests under the worst-case scenarios, the latency is less than 500 ms. In our experience, this level of latency is generally sufficient for most OT applications to operate without disruption.

7. Production is running at full capacity, and we cannot allow any disconnections. Can Edge devices ensure uninterrupted operation during deployment?
In addition to inline deployment, Edge devices support offline deployment, allowing devices to connect to mirror ports for traffic analysis. If inline deployment isn't feasible for your production environment, you can opt for offline mode. However, in offline mode, the devices will only detect malicious activities and will not take preventive actions.

8. We cannot allow sensitive data to be disclosed. What information will be collected by Edge devices?
Although Edge devices deployed in the field will collect asset and communication traffic information, the data will be exclusively stored on the on-premises CMS and will not be uploaded to any public sites.

9. We use some proprietary protocols in OT networks. Will Edge devices block these proprietary packets if they can't recognize them?
This might happen, which is why we recommend initially running Edge devices in monitoring mode. If users are willing to share the proprietary protocol data with us, we can further discuss including it in our protocol support list.

10. If a physical port of an Edge device is damaged, what should be done to ensure uninterrupted network traffic?
Since EdgeIPS Pro is equipped with multiple port pairs, the best option is to quickly switch to spare port pairs for traffic forwarding. Alternatively, you can utilize our newly released universal bypass feature to create redundant uplink ports for traffic continuity.

11. A newly connected tool or HMI suddenly cannot communicate through the Edge device and the production line is stopped. We have no time to tune rules. Is there a quick way to recover the traffic without losing our policy settings?
Starting with Edge firmware v2.3 (EdgeIPS Pro, EdgeIPS) and EdgeOne v2.7, Edge devices support Emergency Mode. Security functions are bypassed so production can continue, while all policy settings remain unchanged. The device still receives traffic for best-effort analysis, so you can keep monitoring the connections. Once the root cause is found and the rule is adjusted, you can restore Normal Mode with one click.

12. What is the difference between Emergency Mode and the hardware bypass / force-open bypass? Which one should we use?
Hardware bypass is triggered automatically when the device loses power, crashes or hangs, and force-open bypass is used for debugging; in both cases the device does not inspect or see the traffic. Emergency Mode is controlled by the operator: the device stays online, keeps its configuration and visibility, and can be switched back from the web console or EdgeOne. We recommend Emergency Mode for communication issues on a running device, while hardware bypass remains the safety net for device failure.

13. Our field operators are not comfortable with an English-only interface. Which languages are supported?
Yes. In firmware v2.3, EdgeIPS Pro and EdgeIPS support more USB disks from multiple vendors for backup, firmware/pattern loading and raw PCAP storage.

14. Our IT department only approves USB disks from certain vendors, and some of them were not recognized by Edge devices before. Has this been improved?
Yes. In firmware v2.3, EdgeIPS Pro and EdgeIPS support more USB disks from multiple vendors for backup, firmware/pattern loading and raw PCAP storage.

Security / Visibility

1. Fab equipment usually contains many internal devices within a small internal network. How do Edge devices protect and detect network traffic sent from internal devices?
Placing an Edge device in front of fab equipment can protect it and filter the bi-directional traffic to and from the equipment. Meanwhile, the Edge device can passively collect asset information from the traffic passing through it.

For support assistance, please contact us at support@txone.com or your Support Provider.