--- sourceDocument: Australia Security Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia Security Management ft:clusterId : - security bundleId : - security workflow : - Technology --- # Define Location # Define Location {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Define a geographic location to provide more context to other STIX Domain Objects (SDOs). ## Before you begin Role required: sn_sec_tisc.analyst ## Procedure 1. Navigate to WorkspacesThreat Intelligence Security Center. 2. Click on Threat Intel Library icon on the workspace. 3. Go to Location object. 4. Click New. Note: Whenever you create new object records for observables, indicators, entities or objects a source record is created and a prompt message is displayed that the new object record is created and then the user is redirected to the aggregated record. 5. On the form, fill in the fields {#tisc-define-location__table_wtw_tcd_nyb__entry__2} | Field | Description | |-|-| | ID | Unique ID for the location. | | Name | Enter a descriptive name to identify the location. | | Description | A description that provides more details and context about the intrusion set, potentially including its purpose and its key characteristics. | | Latitude | The latitude of the Location in decimal degrees. Positive numbers describe latitudes north of the equator, and negative numbers describe latitudes south of the equator. The value of this property must be from -90.0 through 90.0 respectively. | | Longitude | The longitude of the location in decimal degrees. Positive numbers describe longitudes east of the prime meridian and negative numbers describe longitudes west of the prime meridian. The value of this property must be from -180.0 through 180.0, inclusive. | | Precision | Defines the precision of the coordinates specified by the latitude and longitude properties. This is measured in meters. The actual location may be anywhere up to precision meters from the defined point. If this property is not present, then the precision is unspecified. If this property is present, the latitude and longitude properties must be present. | | Region | The region that this location is in. | | Country | The country that this location is in. | | Administrative Area | The state, province, or other sub-national administrative area that this location is in. | | City | The city that this location is in. | | Street Address | The street address that this location describes. This property includes all aspects or parts of the street address. | | Postal Code | The postal code that this location is in. | | Confidence | Enter the confidence for this course of action. | | TLP | TLP (Traffic Light Protocol) is used to ensure that sensitive information is shared with the appropriate audience. It employs four colors (White, Green, Amber, and Red) to indicate different degrees of sensitivity. | | Source | Specifies the threat source from which this object record is created. | | Revoked | Indicates that the revoked objects are no longer considered valid by the object creator. | [Table 1. Identity Details view] {#tisc-define-location__table_wtw_tcd_nyb} {#tisc-define-location__table_xtw_tcd_nyb__entry__2} | Field | Description | |-|-| | Notes | Add any additional notes for this location. | [Table 2. Insights] {#tisc-define-location__table_xtw_tcd_nyb} {#tisc-define-location__table_ytw_tcd_nyb__entry__2} | Field | Description | |-|-| | Additional Context | Add any additional context for this location. | | Spec Version | The version of the STIX specification used to represent this object. The value of this property must be 2.1 for STIX Objects defined according to this specification. | | Lang | This property identifies the language of the text content in this object. | | Created Time In Source | Specifies the time the object is created in the source. | | Extensions | Indicates the extensions for this location. | | Modified Time in Source | Specifies the time the object is modified in the source. | | Processing Status | Represents the processing status of this object, course of action. | | Created | Specifies the time when the record is created in the source. | | Updated | Specifies the time when the record is modified in the source. | | Created By Ref | This property specifies that the identity object that describes the entity had created this object. | [Table 3. Additional Information] {#tisc-define-location__table_ytw_tcd_nyb} 6. Click Save. After you save, a prompt message is displayed indicating that A new observable record is created. Click Continue to edit the record and create new relationships. 7. Click Continue. Important: After you create a new observable record, Prevent System Updates check box is displayed. Select this check box to prevent any updates from the system after the observable or indicator or STIX objects records are created. {#tisc-define-location__table_ztw_tcd_nyb__entry__2} | Field | Description | |-|-| | Tags || | Select Tags | Select the tags that are associated with the location. | | Add Tags | Add new tags. | | Taxonomies || | Select Taxonomy | Select a Taxonomy that is associated with this location. | | Add Taxonomy Values | Add Taxonomy values that are associated with this location. | [Table 4. Tags\&Taxonomies] {#tisc-define-location__table_ztw_tcd_nyb} 8. If you want to delete any record then, select Delete to delete the aggregated record. When you select this action, then it will remove all the related records, except the original source data, and trigger re aggregation. Note: A confirmation message will appear to verify that you want to delete the aggregated record. If you also want to delete the source records and prevent re aggregation, select the Delete Source Records check box. This action will remove all the associated source records. {#tisc-define-location__steps_ybv_yrq_myb} ## What to do next Click any of the following related lists to view additional information about objects associated with the location.{#tisc-define-location__table_b5w_tcd_nyb__entry__2} | Field | Description | |-|-| | External References | Lists the external references which refer to non-STIX information. This property is used to provide one or more external object identifiers. | | Attack Patterns | Lists the attack patterns that help categorize attacks that are associated with this object. | | Campaigns | Lists the campaigns associated with this object. | | Identities | List of identities associated with this object. | | Infrastructure | Lists systems, software services, and any associated physical or virtual resources that are associated with this object. | | Intrusion Sets | Lists a set of adversarial behaviors and resources with common properties associated with this object. | | Malware | Lists the malicious code associated with this object. | | Marketing Definitions | Lists the marketing definitions associated with this object. | | Observables | Lists the observables associated with this object. | | Sightings | Lists the sightings associated with this object. | | Threat Actors | Lists the individuals, groups, or organizations who act with malicious intent associated with this object. | | Tools | Lists legitimate software that is used by threat actors to perform attacks associated with this object. | [Table 5. Related Records] {#tisc-define-location__table_b5w_tcd_nyb} Note: 1. You can link and unlink the related records associated with this object. For more information, see [Link Threat Intel Related Records](https://servicenow-prod.fluidtopics.net/nf4MMSBnawUFJ~BXBWlsVw "Link the records that are related to the corresponding threat intelligence objects."). 2. The various SDOs within the TI library also contains the potential relationships. To establish a relationships between any two objects, you use the Potential Relationships link from the Threat Intel Library to confirm the relationships between the objects. For more information, see [Confirm object-object potential relationships](https://servicenow-prod.fluidtopics.net/0SsxnwCnaa2Zhb6iY_MDtA "Define the potential relationships between the objects."). 3. Also, use the Related Records section from the objects form view to confirm the relationships between two Objects using the Potential Relationships section available on the form view. For more information on see, [Confirm Potential Relationships from Related Records](https://servicenow-prod.fluidtopics.net/TQHhkN60eRr8MHck5BQqaw "Confirm the relationships between the two SDOs."). 4. You can add objects to cases. For more information, see [Add to Case](https://servicenow-prod.fluidtopics.net/A4MS4EYazp9wf3eJgI4hBA "Add observables, indicators, or other objects to the case."). {#tisc-define-location__ol_pmd_bj3_pzb} *[\>]: and then