Contact Assets¶

Contact Assets—comprising Email, Location, and Phone properties—are essential components of comprehensive Attack Surface Intelligence. By organizing contact details with uncovered attributes and relationships, the Open Asset Model reveals connections across diverse resources, supporting a holistic understanding of the asset landscape.

Mirroring the adversary’s perspective, this structure traces discovery paths, contextualizes insights at each contact point, and identifies exposures to strengthen situational awareness.

Collection¶

Complete Contact Coverage: Provides a centralized view of standardized contact asset intelligence across email, location, and phone.
Email Insights: Tracks email connections to link addresses to specific personnel and operational functions, offering visibility into business process maturity.
Location Details: Includes specific location information, from physical addresses and building details to region and locality, for complete geographic context.
Phone Numbers: Captures the relationships between country codes, extensions, and subscriber numbers with individuals and organizational structures.
Connected Data: Traces the contact collection’s discovery path to clarify its origin, validity, and relevance in investigative and data privacy contexts.

OAM Taxonomy

The diagrams and data tables below outline the properties and incoming relationships for each Contact Asset type: Email, Location, and Phone. # (1)!

Required fields are denoted in the data tables.

Email Address¶

Email characteristics offer valuable intelligence for profiling and mapping an organization’s internal structure, operational contacts, and network ownership. Analyzing relationships among contact points makes it possible to trace domain ownership, uncover technical support channels, and reveal security response capabilities. This structured email data enriches the understanding of organizational roles and personnel responsibilities, providing a comprehensive view of the asset landscape through an offensive lens.

Email Requirements

A full email address, formatted as a string, is required for mapping the related relationships.

graph TD
Contact[("Contact Assets")]
Email("Email
Properties")

Email ==> Contact

Person["Person"]
Organization["Organization"]
TLSCertificate["Fingerprint"]
Registration["Registration"]

registrationEmail@{ shape: braces, label: "admin_email
tech_email
billing_email
registrant_email
abuse_email"}

personEmail@{ shape: braces, label: "email"}
tlsEmail@{ shape: braces, label: "subject_email_address"}

registrationEmail --> Email
Registration --o registrationEmail

personEmail --> Email
Person --o personEmail
Organization --o personEmail 

tlsEmail --> Email
TLSCertificate --o tlsEmail

Email Properties¶

Property	Type	Required	Description
`address`	string		The full email address
`local`	string	-	The local part of the email address
`domain`	string	-	The part of the address after the @ symbol

Incoming Relationships¶

Relationship	Type
`admin_email`	`Whois`
`tech_email`	`Whois`
`billing_email`	`Whois`
`registrant_email`	`Whois`
`email`	`Person`
`email`	`Organization`
`abuse_email`	`Registrar`
`subject_email_address`	`TLSCertificate`

Location¶

Property	Type	Required	Description
`formatted_address`	string	-	The formatted address
`building_number`	string	-	the number of the building at the location
`street_name`	string	-	the name of the street at the location
`unit`	string	-	the unit number at the location
`building`	string	-	the name of the building at the location
`town`	string	-	the name town or city at the location
`locality`	string	-	the locality at the location
`region`	string	-	the name of the region or state at the location
`country_code`	string	-	the ISO 3166-1 alpha-2 country code
`postal_code`	string	-	the postal code at the location

Incoming Relationships¶

Relationship	Type
`admin_location`	`Whois`
`tech_location`	`Whois`
`billing_location`	`Whois`
`registrant_location`	`Whois`
`location`	`Person`
`location`	`Organization`
`subject_state_or_province`	`TLSCertificate`
`subject_locality`	`TLSCertificate`

Phone¶

Property	Type	Required	Description
`type`	string	-	The type of phone number
`raw`	string		The raw phone number
`e164`	string	-	The E.164 formatted phone number
`country_abbrev`	string	-	The ISO 3166-1 alpha-2 country code
`country_code`	string	-	The ISO 3166-1 numeric country code
`subscriber_number`	string	-	The subscriber number
`ext`	string	-	The extension of the phone number

Incoming Relationships¶

Relationship	Type
`admin_phone`	`Whois`
`tech_phone`	`Whois`
`billing_phone`	`Whois`
`registrant_phone`	`Whois`
`phone_number`	`Person`
`phone_number`	`Organization`
`abuse_phone`	`Registrar`