Mobile Repositories
The mobile repository is a local type that stores data from various servers. For more information, see Add a Repository.
Configure the following options for all mobile repository types.
| Option | Description | Default |
|---|---|---|
|
Name |
The repository name. |
-- |
|
Description |
(Optional) A description for the repository. |
-- |
|
Type |
The type of repository you want to configure. Your Type selection determines the type-specific options you must configure: ActiveSync Options, AirWatch MDM Options, Apple Profile Manager Options, |
-- |
|
Organizations |
Specifies which organizations have access to the vulnerability data stored in the repository. If groups are configured for the organization, Tenable.sc prompts you to grant or deny access to all of the groups in the organization. For more granular control, grant access within the settings for that group. |
-- |
The following table describes the additional options to configure when creating an ActiveSync mobile repository.
| Option | Description | Default |
|---|---|---|
| Domain Controller | (Required) The domain controller for ActiveSync. | -- |
| Domain | (Required) The Windows domain for ActiveSync. | -- |
| Domain Username | (Required) The username for the domain administrator's account that Tenable.sc uses to authenticate to ActiveSync. | -- |
| Domain Password | (Required) The password for the domain administrator user. | -- |
| Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
| Update Schedule |
Sets the schedule for the MDM server to be scanned to update the mobile repository. On each scan, the current data in the repository is removed and replaced with the information from the latest scan. |
Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating an AirWatch MDM mobile repository.
| Option | Description | Default |
|---|---|---|
| AirWatch Environment API URL | (Required) The SOAP URL or REST API URL you want Tenable.sc to use to authenticate with AirWatch. | -- |
| Port |
(Required) The TCP port that AirWatch listens on for communications from Tenable.sc. |
443 |
| Username | (Required) The username for the AirWatch user account Tenable.sc uses to authenticate to AirWatch's REST API. | -- |
| Password | (Required) The password for the AirWatch user. | -- |
| API Key | (Required) The API key for the AirWatch REST API. | -- |
| HTTPS |
When enabled, Tenable.sc connects using secure communication (HTTPS). When disabled, Tenable.sc connects using standard HTTP. |
Enabled |
| Verify SSL Certificate |
When enabled, Tenable.sc verifies that the SSL certificate on the server is signed by a trusted CA. Tip: If you are using a self-signed certificate, disable this setting. |
Enabled |
|
Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
|
Update Schedule |
Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. |
Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating an Apple Profile Manager mobile repository.
| Option | Description | Default |
|---|---|---|
| Server | (Required) The server URL Tenable.sc uses to authenticate with Apple Profile Manager. | -- |
| Port |
(Required) The TCP port that Apple Profile Manager listens on for communications from Tenable.sc. |
443 |
| Username |
The username for the Apple Profile Manager user account Tenable.sc uses to authenticate to Apple Profile Manager. |
-- |
| Password | The password for the Apple Profile Manager user. | -- |
| HTTPS |
When enabled, Tenable.sc connects using secure communication (HTTPS). When disabled, Tenable.sc connects using standard HTTP. |
Enabled |
| Verify SSL Certificate |
When enabled, Tenable.sc verifies that the SSL certificate on the server is signed by a trusted CA. Tip: If you are using a self-signed certificate, disable this setting. |
Enabled |
|
Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
|
Update Schedule |
Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. |
Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating a Blackberry UEM mobile repository.
| Option | Description | Default |
|---|---|---|
| Blackberry UEM Hostname | (Required) The hostname for the Blackberry UEM server. | -- |
| Blackberry UEM Port | (Required) The port you want Tenable.sc to use for authenticating to the Blackberry UEM server. | -- |
| Blackberry UEM Tenant | (Required) The SRP ID value in Blackberry UEM. | -- |
| Blackberry UEM Domain | The domain name value in Blackberry UEM. | -- |
| Blackberry UEM Username |
(Required) The username for the Blackberry UEM user account Tenable.sc uses to authenticate to Blackberry UEM. |
-- |
| Blackberry UEM Password | (Required) The password for the Blackberry UEM user. | -- |
| Blackberry UEM SSL |
When enabled, Tenable.sc uses an encrypted connection to authenticate with Blackberry UEM. |
Disabled |
| Blackberry UEM Verify SSL Certificate |
When enabled, Tenable.sc verifies that the SSL certificate on the server is signed by a trusted CA. Tip: If you are using a self-signed certificate, disable this setting. |
Disabled |
| Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
| Update Schedule | Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. | Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating a Good MDM mobile repository.
| Option | Description | Default |
|---|---|---|
| Server | (Required) The server URL Tenable.sc uses to authenticate with Good MDM. | -- |
| Port |
(Required) The TCP port that Good MDM listens on for communications from Tenable.sc. |
-- |
| Domain | (Required) The domain name for Good MDM. | -- |
| Username |
(Required) The username for the Good MDM user account Tenable.sc uses to authenticate to Good MDM. |
-- |
| Password | (Required) The password for the Good MDM user. | -- |
| HTTPS |
When enabled, Tenable.sc connects using secure communication (HTTPS). When disabled, Tenable.sc connects using standard HTTP. |
Enabled |
| Verify SSL Certificate |
When enabled, Tenable.sc verifies that the SSL certificate on the server is signed by a trusted CA. Tip: If you are using a self-signed certificate, disable this setting. |
Enabled |
|
Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
|
Update Schedule |
Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. |
Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating a Microsoft Intune mobile repository.
| Option | Description | Default |
|---|---|---|
| Intune Tenant | (Required) The Microsoft Azure Directory value in your Microsoft Intune registration. | -- |
| Intune Client | (Required) The Microsoft Azure Application value generated during your Microsoft Intune registration. | -- |
| Intune Secret | (Required) The Microsoft Azure client secret key. | -- |
| Intune Username |
(Required) The username for the Microsoft Intune user account Tenable.sc uses to authenticate to Microsoft Intune. |
-- |
| Intune Password | (Required) The password for the Microsoft Intune user. | -- |
| Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
| Update Schedule |
Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. |
Every day at 12:30 -04:00 |
The following table describes the additional options to configure when creating a Mobile Iron mobile repository.
| Option | Description | Default |
|---|---|---|
| MobileIron VSP Admin Portal URL | (Required) The server URL Tenable.sc uses to authenticate to the MobileIron administrator portal. | -- |
| VSP Admin Portal Port |
The TCP port that the MobileIron administrator portail listens on for communications from Tenable.sc. |
-- |
| MobileIron Port |
(Required) The TCP port that MobileIron listens on for communications from Tenable.sc. |
443 |
| Username |
(Required) The username for the MobileIron administrator account Tenable.sc uses to authenticate to MobileIron. |
-- |
| Password | (Required) The password for the MobileIron administrator user. | -- |
| HTTPS |
When enabled, Tenable.sc connects using secure communication (HTTPS). When disabled, Tenable.sc connects using standard HTTP. |
Enabled |
| Verify SSL Certificate |
When enabled, Tenable.sc verifies that the SSL certificate on the server is signed by a trusted CA. Tip: If you are using a self-signed certificate, disable this setting. |
Enabled |
| Scanner |
(Required) Specifies which Nessus scanner Tenable.sc uses when scanning the server. Tenable.sc can only use one Nessus scanner to add data to a mobile repository. |
-- |
| Update Schedule |
Specifies when Tenable.sc scans the server to update the mobile repository. On each scan, Tenable.sc removes the current data in the repository and replaces it with data from the latest scan. |
Every day at 12:30 -04:00 |