Keep one register of everything you own
Your clouds, directory and CMDB feed one register that Command, ATLAS and BAIT all read.
- 1MESHMESH
Understand what MESH does
One register for every product. The assets you register in Command, the hosts ATLAS discovers and the resources imported from your sources all land in the same register. Command, ATLAS and MESH show the same records.
Open this step → - 2MESHConnecting sources
Check what each source needs
See also the Onboarding checklist.
Open this step → - 3
- 4MESHConnecting sources
Check the state of your sources
Connected sources shows one card per connection. The summary at the top says how many connections are shown and whether "All connections verified" or how many need attention. Use Search connections… to find one by account name or provider.
Open this step → - 5MESHReview queue and import history
Answer import questions in Command
An Admin or CISO in Command does this.
Open this step → - 6
- 7MESHMESH
Add context and relationships
Admins can do this. A context entity is something that matters to your organisation but that no source reports: a business service, a team, a person, a building, a rack.
Open this step → - 8CommandAssets
Register an asset in Command
Who can do this: Admin and Security manager.
Click Register asset.
Open this step → - 9CommandAssets
Protect it with controls
Who can do this: Admin and Security manager run the analysis. Admin, Security manager and Policy editor can tie controls to assets.
Command can find which of your existing controls already protect an asset, and help you draft a new one for the gap.
Open this step → - 10CommandAssets
Retire what you no longer run
Who can do this: Admin and Security manager.
Command never deletes assets. When an asset is no longer in use, retire it.
Open this step →