This endpoint gives access to the list of targets (also called “affected components”) found when scanning the apps.
See the Introduction for an overview of the API and information relevant to all API operations.
In the Data Theorem portal, each target is shown in the “Affected Components” section when looking at a specific finding:
This endpoint provides a JSON object with a targets
and a pagination_information
key. The targets
key contains a
summary of all target information for issues within a DataTheorem’s customer’s apps in addition to its status history
while the pagination_information
key provides cursor based pagination details for the JSON object response.
In addition to the targets data, the JSON object contains links to other API resources related to the current resource and a link to the issue on the customer facing portal for the linked target.
The JSON object response can be filtered based on the following query parameters:
field | type | description |
---|---|---|
cursor | string | retrieve a paginated list of targets using the specified cursor |
mobile_app_id | integer | filters the list of targets related to the specified app by id |
results_since | string | filters the list of targets based upon when they last had activity due to scans |
security_finding_id | string | filters the list of targets based on the specified security finding by id. |
status_group | string | filters the list of targets based on their current status group |
issue_type_id | string | filters the list of targets based on the specified issue type by id. |
status_group - has the following supported values:
CLOSED
OPEN
For the JSON response, here are all possible values that are returned from the API:
id - The ID that uniquely identifies the security finding target
mobile_app_id - The ID of the mobile app within which this security finding target was identified
security_finding_id - The ID of the security finding to which this security finding target belongs
issue_type_id - The ID of the security finding target’s type of security issue
current_status
OPEN
NEW
CLOSED_FIXED
CLOSED_PARTIALLY_FIXED
CLOSED_WONT_FIX
CLOSED_BY_POLICY
CLOSED_RISK_ACCEPTED
CLOSED_COMPENSATING_CONTROL
CLOSED_ITEM_NOT_FOUND
OPEN_READY_TO_RESCAN
current_status_date - The date the target’s current status was last updated
statuses - A list of all the statuses that this target has historically held
text - A string describing the affected component within the app
links - A list of preformatted paths to other endpoints
portal_url - A link to view the security finding target within the Data Theorem portal
results_last_updated - The date when the security results for this app were last updated
external_id - The ID of this target within an external bug tracker, if an integration has been set up
external_bug_tracker_url - A link to this target within an external bug tracker, if an integration has been set up
additional_contexts - A list of markdown texts describing additional information associated with the target. Often used to help track down where within the app an issue is located
associated_sdk_ids - A list of SDK IDs that Data Theorem has detected are related to this target
1 | GET https://api.securetheorem.com/apis/mobile_security/results/v2/security_finding_targets |
1 | { |
This endpoint provides a JSON object which contains a summary of a specific target for an issue within a DataTheorem’s
customer’s app specified by a security_finding_target_id
.
1 | GET https://api.securetheorem.com/apis/mobile_security/results/v2/security_finding_targets/:security_finding_target_id |
1 | { |
This endpoint provides the ability to update an optional external_id
field on a target. The external_id
field
should represent the id provided by an external bug tracking system such as Jira for tracking the issue. The endpoint
does not provide the ability to edit any other fields on a target.
1 | PATCH https://api.securetheorem.com/apis/mobile_security/results/v2/security_finding_targets/:security_finding_target_id |
1 | {"external_id": "JIRA-12345"} |
The response is similar to a GET request for a Security Finding Target with the optional updated external_id
field
included in the response.
This endpoint overrides the current status of an existing target. The endpoint is meant to be used by API clients to close or re-open certain targets. Upon success a 204 status code is returned with an empty response body.
The endpoint can be used in two ways:
"CLOSED_WONT_FIX"
, "CLOSED_RISK_ACCEPTED"
or "CLOSED_COMPENSATING_CONTROL"
"OPEN"
If the new status is equal to the current status, the request will fail with a 409 status code.
If a reason is provided within the request payload, it will be posted as an internal note on the corresponding finding.
The endpoint expects a JSON object to be passed in the request body.
Field | Required | Type | Description |
---|---|---|---|
status |
✔️ | string | accepted values are "CLOSED_WONT_FIX" , "CLOSED_RISK_ACCEPTED" , "CLOSED_COMPENSATING_CONTROL" , "OPEN" |
reason |
string | justification for changing the status |
1 | POST https://api.securetheorem.com/apis/mobile_security/results/v2/security_finding_targets/:security_finding_target_id/statuses |
JSON body:
1 | { |
1 | HTTP/2 204 No Content |
Empty body.