License Metrics

 

Node:

A node is a Tripwire Enterprise object that represents a monitored system (database, directory server, file server or network device) on a network.

  • Directory server node
    Represents a physical server or virtual machine that hosts a centrally managed information store that enables users to search for data saved in a variety of locations on a network
  • File server node
    Represents a physical server or virtual machine that hosts a file system (software used to organize and store files)
  • Network device node
    Represents a physical router, switch, firewall, load balancer or UNIX system

 

Instance:

An instance is a physical or virtual object or occurrence.  For example:

  • An instance for TE for VMware ESX is measured per ESX Hypervisor Manager
  • A database instance means one database
  • A Microsoft Exchange instance means the installation of Microsoft Exchange on one operating system
  • A virtual appliance instance means the installation of the virtual appliance on a single operating system instance

 

IP:

An IP is an internet protocol address.  A “Per IP” license means a license based on the number of unique IP addresses scanned per day.  

For IP360, an IP license will be used each time the customer scans a specific and active IP for a vulnerability and as long as the customer has access to those results on the VnE Manager. Customers do not consume a license for scanning empty IP space or for discovery scans that do not include vulnerability scanning. License calculation, which is recalculated daily, is determined by counting all the records currently in the persistent host table that were at any time scanned for vulnerabilities and whose networks are not deleted, and then remove any duplicate IP addresses.

 

Processor:

For file system monitoring and Tripwire for Servers, a processor is defined as a single chip that houses a collection of one or more processor cores.

 

Data Source:

A data source is a Tripwire Enterprise (TE) console instance from which a Connect instance installed on a different TE console instance is aggregating data.

 

License Restrictions

 

For all Tripwire Apps other than Console Orchestrator:

A Tripwire App license includes use on up to two licensed non-production consoles for the purpose of test and disaster recovery.

 

For Console Orchestrator:

A Console Orchestrator App license includes use in one inactive/standby disaster environment.

 

For Tripwire Connect Add-On Extension:

A no-charge Tripwire Connect Add-On Extension is licensed for use with a single supported Tripwire Enterprise (TE) console, for as long as the TE console remains under support. Tripwire will provide support for the Add-On Extension on a TE console as part of the support for the TE console, at no additional charge, under the same support terms (Enterprise or Basic) as Tripwire provides for the TE console. Tripwire Connect Additional Data Source licenses, to allow Tripwire Connect to aggregate data from additional TE sources, are available for purchase.

 

Non- Production License Restrictions:

Software licenses identified as "Non-Production" on an order are designated as available for use in a non-production environment only (“Non-Production Licenses”), and any pricing included on the applicable order reflects this license restriction. Use of these Non-Production Licenses in a capacity other than in the customer's development, test or staging environments is prohibited. Non-Production Licenses can only be run on a Tripwire Enterprise Console that is also licensed under Non-Production License.

Disaster Recovery License Restrictions:

Software licenses identified as “Disaster Recovery” on an order are designated as available for use in test and disaster recovery environments only, and the pricing included on the applicable order reflects this license restriction.