Data management operations
Data management operations are Cyber Vision Center features that
-
manage and optimize data stored on Cyber Vision Center,
-
support tasks such as data clearance, setting data expiration, and customizing data ingestion, and
-
improve system performance by enabling effective storage and retention policies.
|
Feature |
Release Information |
Feature Description |
|---|---|---|
|
Clear multiple components using a VLAN ID |
Release 5.3.x |
When you clear data, you can enter a VLAN ID to purge all the components associated with it. You can clear data for one VLAN ID at a time. |
Caution: Understand the impact before clearing all data
Clear all data only when absolutely necessary, such as when the database becomes overloaded.
Be aware of these consequences:
-
The system deletes all network data, including components, flows, events, and baselines, from Cyber Vision Center.
-
The GUI becomes empty.
-
The system preserves only configuration settings, such as capture modes, event severity, and syslog settings.
-
Clearing all data disrupts network monitoring.
Data storage and expiration settings
This table explains storage limits, expiration policies, and purge methods for each data type. You can use this information to manage system resources effectively.
|
Data type |
Storage |
Expiration |
|---|---|---|
|
Components or Devices |
Storage is internal only. You receive a warning when you reach 120,000 components. Data ingestion stops at 150,000 components. |
No expiration. Manual purge is needed. |
|
Activities |
Activities are stored internally and do not have a high storage limit. |
The data does not expire. You must purge it manually. |
|
Flows |
You can enable or disable storage configuration; there is no upper storage limit. You can then define networks. |
The system automatically deletes data after seven days of inactivity. |
|
Events |
You can configure the storage for each category, with a high limit of 10,000 per event category. |
No expiration. The oldest event is purged when the 10,000 limit is reached. |
|
External communications |
Communications are stored externally only. You can save up to one million communications. |
The system deletes data automatically after 30 days. |
|
Variables |
You can enable or disable the storage configuration, with no high storage limit. |
The system deletes data automatically after seven days of inactivity. |
|
Reports |
You can set the storage period from three months to three years. The default is six months. The storage duration also depends on the maximum number of versions you set. |
The system automatically deletes data when the creation date is older than the defined period or when the number of versions exceeds the limit. |
Purge components from the database
Remove unnecessary or obsolete network components and devices to maintain optimal database performance and prevent data ingestion issues.
To protect the database, the system limits the number of components such as network interfaces, PCs, SCADA stations, broadcast or multicast addresses, and similar items.
-
If the count exceeds 120,000, a pop-up and red banner alert you to purge.
-
When the number of components reaches 150,000, data ingestion stops. The system deletes new data without processing or storing it. A pop-up and red banner alert you to purge.
Before you begin
-
Ensure you have Admin access.
Procedure
|
Step 1 |
From the main menu, choose Admin > Data Management > Clear Data. |
|
Step 2 |
Select Components selection. |
|
Step 3 |
Choose the Component Type:
|
|
Step 4 |
Specify any criteria for purging (all fields optional):
|
|
Step 5 |
Click Clear data and confirm when prompted. |
The database removes the specified components and related devices. The updated device count appears under Explore > All Data.
![]() Note |
Purging components by VLAN, IP, or date triggers an event. If a Global Center is enrolled, those components are also purged in the Global Center after synchronization. |
What to do next
Review the device list to ensure the correct components were removed.
Expiration settings
Expiration settings help you manage system storage and performance.
Key aspects of expiration settings:
-
Expiration settings control the retention period and number of versions for reports only. Other data types (such as Components, Devices, Activities, Flows, Events, External communications, and Variables) have fixed retention periods.
-
Expiration settings manage storage consumption by automatically purging reports older than the configured retention period.
-
Increasing the retention period increases storage usage and may negatively impact system performance.
-
Access expiration settings at Admin > Data Management > Expiration Settings in the Cyber Vision Center interface.
Ingestion configurations
An ingestion configuration is a data management feature that determines whether flow and variable traffic data are stored and processed by Cyber Vision Center.
You can enable or disable storage of flows and variables. By default, both options are disabled. To limit data storage, you can specify which flows from subnetworks are stored. These subnetworks are defined within Network Organization settings.
If flows and variables are disabled, data will not be stored in the database.
Flows Aggregation
-
Cyber Vision records each flow that it detects, and includes details such as client and server ports for your reference.
-
For protocols such as DNS, HTTP, or SSH, client ports can vary, so you may see many similar entries in your data.
-
If you enable Flow Aggregation, Cyber Vision does not consider the client port for those specific protocols. This combines similar flows and limits the number of records in the database.
Port scan detection
Port scan detection helps you identify and respond to suspicious network probing, which may indicate cyberattack attempts.

Feedback