MarkMonitor
Visualize MarkMonitor domains, DNS zones, DNS records, contacts, and domain groups, and monitor changes through queries and alerts including domain audit logs for compliance tracking.
- Installation
- Data Model
- Types
Installation
Prerequisites in MarkMonitor
To use this integration, you need API credentials from MarkMonitor. These credentials are not self-service and must be obtained through your MarkMonitor account representative or Designated Partner Administrator (DPA).
Required Credentials
You will need the following credentials from your MarkMonitor account:
- API Key - Used for the
X-API-KEYheader in all API requests - Username - Your MarkMonitor API username (typically an email or service account)
- Password - Your MarkMonitor API password
Obtaining API Credentials
- Log in to the MarkMonitor Customer Portal
- Contact your MarkMonitor account representative or DPA to request API access
- Once approved, you will receive:
- An API key for authentication
- API username and password credentials
- Ensure your account has appropriate permissions to access the Domain API
For more information about the MarkMonitor APIs, refer to the MarkMonitor API Documentation.
Optional: DNS API Access
The integration can also ingest DNS records if your account has access to the MarkMonitor DNS API. This requires separate authentication and may not be available for all customers. Contact your MarkMonitor representative to verify DNS API access.
Configuration in JupiterOne
To install the MarkMonitor integration in JupiterOne, navigate to the Integrations tab and select MarkMonitor. Click New Instance to begin configuring your integration.
Creating an instance requires the following:
-
Account Name used to identify the MarkMonitor account in JupiterOne. Ingested entities will have this value stored in
tag.AccountNamewhen the Tag with Account Name option is enabled. -
Description to assist in identifying the integration instance, if desired.
-
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration. -
API Key - Your MarkMonitor API key for X-API-KEY header authentication.
-
Username - Your MarkMonitor API username.
-
Password - Your MarkMonitor API password.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Entities
The following entities are created:
| Resources | Entity _type | Entity _class |
|---|---|---|
| Account | markmonitor_account | Account |
| AuditLog | markmonitor_audit_log | Record |
| Contact | markmonitor_contact | Person |
| DnsRecord | markmonitor_dns_record | DomainRecord |
| Domain | markmonitor_domain | Domain |
| DomainZone | markmonitor_domain_zone | DomainZone |
| Group | markmonitor_group | Group |
| Nameserver | markmonitor_nameserver | Gateway |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
|---|---|---|
markmonitor_account | HAS | markmonitor_group |
markmonitor_account | HAS | markmonitor_domain |
markmonitor_account | HAS | markmonitor_contact |
markmonitor_domain | HAS | markmonitor_domain_zone |
markmonitor_domain | HAS | markmonitor_audit_log |
markmonitor_domain_zone | USES | markmonitor_nameserver |
markmonitor_domain_zone | HAS | markmonitor_dns_record |
markmonitor_group | HAS | markmonitor_domain |
Markmonitor Account
markmonitor_account inherits from Account
| Property | Type | Description | Specifications |
|---|---|---|---|
accountId * | string |
Markmonitor Audit Log
markmonitor_audit_log inherits from Record
| Property | Type | Description | Specifications |
|---|---|---|---|
domainName * | string | ||
userName * | string | null |
Markmonitor Contact
markmonitor_contact inherits from Person
| Property | Type | Description | Specifications |
|---|---|---|---|
contactId * | string | ||
contactType * | string | null | ||
organization * | string | null |
Markmonitor Dns Record
markmonitor_dns_record inherits from DomainRecord
| Property | Type | Description | Specifications |
|---|---|---|---|
comment * | string | null | ||
port * | number | null | ||
priority * | number | null | ||
recordId * | number | ||
weight * | number | null | ||
zoneId * | string | ||
zoneName * | string | null |
Markmonitor Domain
markmonitor_domain inherits from Domain
| Property | Type | Description | Specifications |
|---|---|---|---|
adminId * | string | null | ||
billingId * | string | null | ||
group * | string | null | ||
paidThroughDate * | number | null | ||
registrantId * | string | null | ||
renewalStatus * | string | null | ||
techId * | string | null |
Markmonitor Domain Zone
markmonitor_domain_zone inherits from DomainZone
| Property | Type | Description | Specifications |
|---|---|---|---|
dnssecAlgorithm * | string | null | ||
dnssecDigest * | string | null | ||
dnssecDigestType * | number | null | ||
dnssecEnabled | boolean | ||
dnssecKeyTag * | number | null | ||
dnssecRecords | array of undefineds | ||
nameservers | array of strings |
Markmonitor Group
markmonitor_group inherits from Group
| Property | Type | Description | Specifications |
|---|---|---|---|
domainCount * | number | null | ||
groupId * | string |
Markmonitor Nameserver
markmonitor_nameserver inherits from Gateway
| Property | Type | Description | Specifications |
|---|---|---|---|
fqdn * | string |