Detailed system requirements

This section provides comprehensive information on the system requirements for Integration Services. Prior to service deployment, it is necessary for the user to possess the access outlined below.

BigFix Service Account Requirements

  • admin access (not SOAP role admin access)

To facilitate the import of ServiceNow CMDB data into BigFix, a Master Operator account is required. Otherwise, the minimum account requirements to send BigFix endpoint data to ServiceNow are the following:

  • A non-master operator account with permissions against the in-scope computers.

  • Read access to the BigFix ServiceNow Data Flow site.

  • The Can use REST API setting set to Yes

  • The Can Create Actions setting set to No.

ServiceNow Service Account Requirements

  • Read and write access for CMDB_CI_COMPUTERS , SYS_CHOICE and CORE_COMPANY tables

  • The ServiceNow Administrator should have a service account that leverages basic authentication with read and write access to the CMDB tables.

Important: While running the BigFix ServiceNow integration from ServiceNow to BigFix, it's crucial to ensure that user roles align with the table's Access Control List (ACL) for successful attribute extraction. If there's a mismatch between user roles and the table's ACL, users may encounter instances of empty data.
Table 1. ServiceNow Data Flow
Prerequisites Operating system Hardware Configuration BigFix Service Account Supported BigFix versions Supported ServiceNow versions Recommendations
Microsoft VC++ Redistributable package 2012. Install it from Microsoft website.
  • Windows 2016
  • Windows 2019
  • 6-8 Cores
  • 32 GB RAM
RAM Utilization depends on number of devices, example:
  • 50k devices utilize 3.5GB RAM
  • 300k devices utilize 22GB RAM*
  • Network Access to BigFix Root Server
  • Network Access to ServiceNow REST APIs
  • Master Operator account required
  • Access to InScope Devices
  • No Ability to Create Actions
  • Access to REST API
  • Access to Any Site Containing In-Scope Properties
 BigFix Server version 10
  • Orlando
  • Madrid
  • New York
  • Rome
  • Quebec
  • Paris
  • San Diego
  • Tokyo
  • Utah
  • Vancouver
 In larger environments, make sure you deploy the integration solution on a dedicated server.

*12 hours execution for 300K devices consumes maximum 22 GB RAM