Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Assets Data Manager for Jira Service Management Cloud is a Premium and Enterprise only feature that is currently in Open Beta development. View and vote on our list of upcoming features.
If you find a bug or have questions, please reach out to Atlassian Support or the Atlassian Community.
Falcon is a tool produced by CrowdStrike. It is an Endpoint Detection and Response (EDR) software. It monitors the devices on which it’s installed to look for signs of malicious activity and help to lock down the threats.
Falcon Adapter uses an API connection to bring data into Assets Data Manager.
This task requires Data Manager Adapters admin permissions to complete. See how permissions and roles work in Data Manager.
Follow this procedure to connect this tool to Assets Data Manager using the custom-built Adapter:
Gather all of the information listed in the Data Manager Fields section, such as the Name, Object class, Data Source Name, and Data Source Type.
Gather all of the information in the Falcon Fields section - this may require consultation with the subject matter expert (SME) for Falcon.
Within Data Manager:
Create a new job by selecting the Adaptor that matches your tool.
Configure all of the required fields with the appropriate information.
Within Falcon:
Follow all of the steps listed in the Authentication and Authorization section, below, to properly configure Authentication and Authorization.
Review the information in the API Call section, below to understand the call.
Review the information in the Fields Retrieved section, below.
Each time this job is run, the data your have selected will be brought into Data Manager using the configured Adapter and become raw data.
You will need to specify the following information from Assets Data Manager:
Name - the name of the connection, visible as the job name in Adapters.
Object Class - the name of the Object Class you want to the data to be loaded into.
Data Source Name - the type of data being created; which is usually the tool name, e.g AD, Qualys etc. Note: This can be the same as Name.
Data Source Type - what type of data is the tool providing? For example, Assets, CMDB, user location and more.
You will need to specify the following information from Falcon:
API URL: the API URL to access the Crowdstrike source.
Client ID: the Client ID created when the account is set-up through Crowdstrike.
Client Secret: the secret string created when the account is set-up through Crowdstrike.
API Limit: sets the page size of API results. The Api Limit field allows the enforcement of the amount of request/quantity of data (or records) to be consumed by the Data Manager and transferred to the back-end staging database.
By default, the API limit is set to 5000. However if the source is heavily populated with data, the best practice is to limit the rate to 1000. This API limit can be adjusted between 1 and 5000 until results are returning successfully.
Create API clients to grant various levels of API access for different purposes.
From the API Clients and Keys page, click Add new API client in the OAuth2 API Clients table.
Provide details to define your API client: Client Name(required), Description (optional), API scopes.
Click Add to save the API client and generate the client ID and secret.
The API call for Falcon is: Device.Read.All.
The Adapters Client directly calls the API to retrieve a list of resources (Devices).
API: {api-url}/devices/queries/devices-scroll/v1?limit={apiLimit}
Method: GET
Response: A list of:
Meta (query_time, pagination, powered_by, trace_id), resources (a list of strings), errors
It then uses the resources (device IDs) to call the API and retrieve device information.
API: {api-url}/devices/entities/devices/v2
Method: POST
Response: See the Fields Retrieve section below.
The following fields are retrieved:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
DeviceId
Cid
AgentLoadFlags
AgentLocalTime
AgentVersion
BiosManufacturer
BiosVersion
ConfigIdBase
ConfigIdBuild
ConfigIdPlatform
CpuSignature
ExternalIp
MacAddress
InstanceId
ServiceProvider
ServiceProviderAccountId
Hostname
FirstSeen
LastSeen
LocalIp
MajorVersion
MinorVersion
OsVersion
PlatformId
PlatformName
ReducedFunctionalityMode
PreventionPolicyId
PreventionApplied
PreventionSettingsHash
PreventionAssignedDate
PreventionAppliedDate
SensorUpdatePolicyId
SensorUpdateApplied
SensorUpdateSettingsHash
SensorUpdateAssignedDate
SensorUpdateAppliedDat
SensorUpdateUninstallProtection
DeviceControlPolicyId
DeviceControlApplied
DeviceControlAssignedDat
DeviceControlAppliedDate
GlobalConfigPolicyId
GlobalConfigApplied
GlobalConfigSettingsHash
GlobalConfigAssignedDate
GlobalConfigAppliedDat
RemoteResponsePolicyId
RemoteResponseApplied
RemoteResponseSettingsHash
RemoteResponseAssignedDate
RemoteResponseAppliedDate
AirlockPolicyId
AirlockApplie
AirlockSettingsHash
AirlockAssignedDate
AirlockAppliedDate
AirlockVersion
FirewallPolicyId
FirewallApplied
FirewallAssignedDate
FirewallAppliedDate
FirewallRuleSetId
Groups
GroupHash
ProductTypeDesc
SerialNumber
Status
SystemManufacturer
SystemProductName
Tags
ModifiedTimestamp
QueryTim
PoweredBy
TraceId
Version
VersionString
ZoneGroup
KernelVersion
ChassisType
ChassisTypeDesc
ConnectionIp
DefaultGatewayIp
ConnectionMacAddress
LinuxSensorMode
DeploymentType
ProvisionStatus
BuildNumber
OsBuild
Ous
ManagedAppsAirlockPolicyId
ManagedAppsAirlockApplied
ManagedAppsAirlockSettingsHash
ManagedAppsAirlockAssignedDate
ManagedAppsAirlockAppliedDate
ManagedAppsAirlockVersion
ProductType
ServicePackMinor
PointerSize
SiteName
OsProductName
LastReboot
MachineDomain
ServicePackMajor
DetectionSuppressionStatus
Was this helpful?