Asset Attestation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 09:16 AM
To deploy asset attestion what all tables are required to be integrated?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 12:06 PM
Hi @gladwingun ,
From my experience below are the key tables that needs to integrated for Asset Attestation:
alm_asset, alm_hardware, alm_model, cmdb_ci, sys_user, cmn_department, cmn_location, sn_attestation_definition, sn_attestation_task, sn_attestation_response
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2025 07:51 AM
Hi @gladwingun ,
As per my understanding , Below are the table with details.
Purpose | Table | Notes |
Asset repository | alm_asset | Stores all IT assets (hardware, software, consumables, etc.). |
Hardware assets | alm_hardware | Subclass of alm_asset specifically for hardware. |
Configuration Items | cmdb_ci (and subclasses like cmdb_ci_computer, cmdb_ci_server, etc.) | Needed when asset and CI data must be reconciled. |
Attestation definitions | cmdb_data_certification | Defines what is certified, frequency, owner, etc. |
Attestation schedule | cmdb_data_certification_schedule | Controls when and how often attestation runs. |
Attestation tasks | cmdb_data_certification_task | Individual tasks assigned to users/groups to review and attest assets. |
Attestation controls | cmdb_data_certification_control | Stores the specific checks/controls run as part of attestation. |
User info | sys_user, sys_user_group |
Needed to route tasks to asset owners, managers, etc.
|
Integration context: why each is needed
* alm_asset & alm_hardware → actual asset records you want to attest.
* cmdb_ci → link asset records to CIs for accuracy & completeness.
* cmdb_data_certification → drives the attestation campaign.
* cmdb_data_certification_task → creates review tasks assigned to people.
* sys_user / sys_user_group → identify asset owners who perform attestation.
Steps when deploying:
1. Identify the assets / CI classes to be attested.
2. Define attestation policy:
* Frequency (quarterly, annually, etc.)
* Who will attest (assigned owners, managers, etc.)
3. Configure or customize:
* Data certification definition (cmdb_data_certification)
* Scheduling (cmdb_data_certification_schedule)
4. Map asset owner:
* Use fields like owned_by, managed_by, or custom logic to assign tasks.
5. Run certification → system creates tasks in cmdb_data_certification_task.
6. Owners complete tasks; results tracked.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025