.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-04-27T15%3A33%3A04Z&se=2024-04-27T15%3A43%3A04Z&sp=r&sig=W8QmUkL8Fe4mscgGYNIAgKQlKVJflrq65%2FVTOmb0dHk%3D){kind=logo}
SNIPE-IT - Create Asset
- 28 Jan 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
SNIPE-IT - Create Asset
- Updated on 28 Jan 2024
- 3 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
SNIPE-IT - Create Asset creates or updates assets in SNIPE-IT for:
- Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Use stored credentials from the SNIPE-IT adapter - Select this option to use (the first) SNIPE-IT connected adapter credentials.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Required Fields
These fields are required to run the Enforcement Set.
- Status ID - The ID of the related status label.
- Model ID - The ID of the related asset model.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Note:
If Use stored credentials from the SNIPE-IT adapter is not enabled, these fields are required.
- SNIPE-IT Domain - The domain of the SNIPE-IT server.
- API Key - In order to use the API, you’ll need to generate an API key that will be associated with your user. Generating API Tokens
Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- Action Choice - Select the action to perform:
- Create - Only create new assets and ignore existing ones.
- Create and Update - Create new assets and update existing ones.
- Update - Only update existing assets and ignore new ones.
Exclude connections - From the list, select the adapter connections to ignore. You can select more than one.
Map Axonius fields to adapter fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.
Note:For details, see Axonius to External Field Mapping.
- Asset Tag - The asset tag of the asset being created or updated. If auto-incrementing is enabled in SNIPE-IT settings, this is not required and will be automatically generated.
APIs
Axonius uses the SNIPE-IT API.
Required Permissions
Personal Access Tokens reflect the permissions of the user the token is associated with. For example, if a user is only allowed to view assets but not update them, any API requests made using that user’s Personal Access Token will return an Unauthorized error if they attempt to perform an action their regular logged-in user isn’t permitted to do, such as updating an asset.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?