Location
A Location represents a geographic location. The location may be described as any, some or all of the following: region (e.g., North America), civic address (e.g. New York, US), latitude and longitude.
Locations are primarily used to give context to other SDOs. For example, a Location could be used in a relationship to describe that the Bourgeois Swallow intrusion set originates from Eastern Europe.
The Location SDO can be related to an Identity or Intrusion Set to indicate that the identity or intrusion set is located in that location. It can also be related from a malware or attack pattern to indicate that they target victims in that location. The Location object describes geographic areas, not governments, even in cases where that area might have a government. For example, a Location representing the United States describes the United States as a geographic area, not the federal government of the United States.
At least one of the following properties/sets of properties MUST be provided:
- region
- country
- latitude and longitude
When a combination of properties is provided (e.g. a region and a latitude and longitude) the more precise properties are what the location describes. In other words, if a location contains both a region of northern-america and a country of us, then the location describes the United States, not all of North America. In cases where a latitude and longitude are specified without a precision, the location describes the most precise other value.
If precision is specified, then the datum for latitude and longitude MUST be WGS 84 [WGS84]. Organizations specifying a designated location using latitude and longitude SHOULD specify the precision which is appropriate for the scope of the location being identified. The scope is defined by the boundary as outlined by the precision around the coordinates.
Properties
Property | Type | Description |
---|---|---|
type optional | string | The type of this object, which MUST be the literal `location`. |
description optional | string | A textual description of the Location. |
name optional | string | A name used to identify the Location. |
latitude optional | number | The latitude of the Location in decimal degrees. |
longitude optional | number | The longitude of the Location in decimal degrees. |
precision optional | number | Defines the precision of the coordinates specified by the latitude and longitude properties, measured in meters. |
region optional | string | The region that this Location describes. |
country optional | string | The country that this Location describes. |
administrative_area optional | string | The state, province, or other sub-national administrative area that this Location describes. |
city optional | string | The city that this Location describes. |
street_address optional | string | The street address that this Location describes. |
postal_code optional | string | The postal code for this Location. |
Relationships
These are the relationships explicitly defined between the Location object and other STIX Objects. The first section lists the embedded relationships by property name along with their corresponding target. The rest of the table identifies the relationships that can be made from this object type to another object type by way of the Relationship object. The reverse relationships section illustrates the relationships targeting this object type from another object type. They are included here for convenience. For their definitions, please see the "Source" object.
Relationships are not restricted to those listed below. Relationships can be created between any objects using the related-to relationship type or, as with open vocabularies, user-defined names.