- Knowledge base
- Users
- Teams
-
Security updates
-
Product news
-
Next-Gen Vulnerability Management
-
Getting started
-
General
-
Operating status
-
Network & System Security
-
Web Application Security
-
Cloud Security
-
API Security
-
Phishing Simulation & Awareness Training
-
Attack Surface Management
-
Scanner Appliance
-
Device Agent
-
On-premise platform deployment
-
Asset management
-
Vulnerability manager
-
Reports
-
Digest reports
-
Organizer
-
Continuous monitoring
-
Integrations
-
Platform API
-
Remediation
-
Users
-
PCI DSS ASV scans
-
Terms & conditions
-
Dashboard
Migration of Asset Owners to Teams
Deprecation Notice: Transition from Individual Asset Ownership to Teams and Tags
As part of our ongoing efforts to streamline asset management and improve scalability, we are announcing the deprecation of the individual user asset ownership feature. Moving forward, assets will be owned either by Teams or by inheriting ownership through Tags.
Why the Change?
Individual ownership of assets has limited scalability, making it challenging to manage responsibility effectively, especially within larger organizations. Transitioning to Team-based ownership or leveraging Tags to inherit ownership helps ensure clarity, ease of management, and improved operational workflows.
What Does This Mean for You?
Starting in Q4 2025, individual users can no longer be assigned as direct asset owners. Existing individually owned assets must transition to ownership via Teams or Tags.
How to Prepare for the Migration:
- Review Your Current Assets: Identify assets currently assigned to individual owners.
- Set Up Teams: Create or designate existing Teams responsible for asset management within your organization.
- Implement Tags: Ensure a clear tagging structure is in place to help assets inherit appropriate ownership effectively.
- Migrate Ownership: Update your assets to assign ownership to the appropriate Team or confirm assets are properly tagged to inherit ownership.
Next Steps
To avoid disruptions, we recommend completing this migration well before the deprecation date. Please contact our support team or refer to our detailed documentation for assistance or additional information.
Thank you for your cooperation and for helping us continuously improve our platform.