The following tables list commonly used entity fields available to Report Templates and Export Templates.

Important: The fields that appear in a report or data export are determined by the user generating the report or exporting data. If the user's role does not allow them to view certain fields, those fields will not appear in the output.

Table 1. Application fields
FieldDescription
idThe Resolve ID of the application.
internetFacingSpecifies if the application is reachable from the internet.
nameThe name of the application.
primaryUrlThe primary URL of the application.
statusThe status of the application
versionThe version of the application.
Table 2. Asset fields
FieldDescription
applicationIdAny application IDs associated with the asset.
assetTypeThe platform that the asset belongs to, such as Microsoft Windows or VMware ESX.
closedFindingsThe number of closed findings associated with the asset.
cvssThe CVSS V2 score of the asset.
cvssV3The CVSS V3 score of the asset.
descriptionThe description of the asset.
dnsThe domain name of the asset.
environmentThe environment the asset is located in.
externalIdentifierAn external or third-party ID of the asset.
findingIdAny finding IDs associated with the asset.
idThe Resolve ID of the asset.
importanceThe business importance of the asset.
ipaddressThe IP address of the asset.
hostNameThe host name of the asset.
lastUpdatedThe date and time the asset was last updated.
masterfindingIdAny master finding IDs associated with the asset.
nameThe asset name.
openFindingsThe number of open findings associated with the asset.
ownerThe person, group, or department responsible for the asset.
projectsIdAny project IDs associated with the asset.
serialnumberThe serial number of the asset.
siteThe site that the asset is located.
Table 3 - Finding Fields 
FieldDescription
assetDescriptionThe description of the asset associated with the finding.
assetIdThe Resolve ID of the asset associated with the finding.
assetNameThe name of the asset associated with the finding.
assetTypeThe type or platform of the asset associated with the finding.
assignedToThe user the finding is assigned to.
assignedToIdThe Resolve ID of the user the finding is assigned to.
businessImpactThe business impact of the finding.
categoryThe category of the finding.
created_onThe date and time the finding was created.
cweThe CWE associated with the finding.
descriptionThe description of the finding.
dnsThe DNS name of the associated asset.
environmentThe environment of the finding.
externalIdentifierThe external ID associated with the finding.
hostNameThe host name of the associated asset.
idThe Resolve ID of the finding.
ipThe IP address of the associated asset.
masterFindingIdThe ID of the correlated master finding.
masterFindingVariationThe name of the finding.
mitreAttackTacticNameThe MITRE Attack Tactic
mitreAttackTechniqueNameThe MITRE Attach Technique
otherReferencesReferences with more information regarding the vulnerability of the finding.
owasp2013VulnerabilityTypeThe OWASP 2013 vulnerability type.
owasp2017VulnerabilityTypeThe OWASP 2017 vulnerability type.
owaspMobile2014VulnerabilityTypeThe OWASP Mobile 2014 vulnerability type.
owaspMobile2016VulnerabilityTypeThe OWASP Mobile 2014 vulnerability type.
pciRequirementThe PCI requirement number.
projectsIdThe Resolve ID of the project that the finding appears in.
remediationDueDateThe remediation due date.
scanIdThe Resolve ID of the scan that the finding appears in.
severityThe severity of the finding.
stateThe state of the finding.
wascVulnerabilityTypeThe WASC vulnerability type. 


Table 4. Project fields
FieldDescription
applicationAssetThe application asset associated with the project.
applicationnameThe application associated with the project.
appSourceCodeIdThe application source code ID associated with the project.
businessUnitThe business unit the project belongs to.
createdThe date and time the project was created.
descriptionThe description of the project.
enddateThe end date of the project duration.
externalEngagementIdThe external engagement ID associated with the project.
externalEngagementNameThe name of the external engagement associated with the project.
externalIdAn external or third-party ID of the project.
externalNameAn external or third-party name of the project.
externalSourceCodeAn external or third-party source code of the project.
idThe Resolve ID of the project
intervalThe recurring time interval of the project.
lastUpdatedThe date and time the project was last updated.
nameThe project name.
projectGroupThe group the project belongs to.
projectTypeThe project type.
scanEndThe end time of the scan associated with the project.
scanStartThe start time of the scan associated with the project.
scopeThe scope of the project.
shortNameA short or truncated name of the project.
startdateThe start date of the project duration.
stateThe state of the project.
validationEndThe end date for validation testing.
validationStartThe start date for validation testing.
verificationEndThe start date for verification testing.
verificationStartThe start date for verification testing.
versionThe application version associated with the project.
Table 5. Scan fields
FieldDescription
endTimeThe end time of the scan.
fileNameThe name of the file that was scanned.
idThe Resolve ID of the scan.
importedOnThe date and time the scan was imported.
masterFindingIdAny master finding IDs associated with the scan.
scanTypeThe scan type.
startTimeThe start time of the scan.
statusThe status of the scan.
Table 6. User fields
FieldDescription
addressThe street address the user works at.
cityThe city the user works in.
countryThe country the user works in.
createdOnThe date the user was created.
defaultDashboardThe default dashboard assigned to the user.
emailThe user's email address.
faxThe user's fax number.
firstNameThe user's first name.
idThe Resolve ID of the user.
lastNameThe user's last name.
lastSignInThe date the user last logged on to Resolve.
mobilePhoneThe user's mobile phone number.
phoneThe user's work or desk phone number.
skipMultifactorA true or false value indicating if multi-factor authentication can be skipped for this user.
sourceTypeThe authentication method used to log in to Resolve, such as LDAP, SAML, or the local Resolve database.
stateThe state the user works in.
statusThe status of the user (active or deactivated).
titleThe user's work title.
userNameThe user's user name for Resolve.
zipThe zip code the user works in.