License Types: Synopsys licenses its Licensed Products and Subscription Services pursuant to the following License Types: The License Types may only be used within the applicable Licensed Product and Subscription Service group described below.
— For Coverity and Coverity on Polaris Licensed Products —
I. LOC License - legacy as of November 1, 2020
An “LOC License” restricts the aggregate number of lines of code in the Code Base on which the Customer may use the Licensed Product. The Licensed Product cannot be used on code exceeding the number of lines of code licensed for use. More information about Synopsys’ LOC License Policy can be found at https://www.synopsys.com/company/legal/software-integrity/line-count-guidelines-v2015-1.html.
II. Team License – legacy as of November 1, 2020
A “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold in 5 User Pack increments and the quantity identified in the Purchasing Agreement identifies the total number of 5 User Packs licensed.
III. Team License – current as of November 1, 2020
A “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases (in some organizations this is referred to as applications or projects) being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold with a minimum size of 10.
A “Team Member” is an individual within the named development team.
— For Codenomicon (Defensics) Licensed Products —
I. Concurrent User License
A “Concurrent User License” restricts the use of the Licensed Product, at any one time, to the maximum number of users identified in the applicable Purchasing Agreement. Use of the Licensed Product is further restricted to use on the Application(s) stated in the applicable Purchasing Agreement.
II. Named User License
A “Named User License” restricts the use of Licensed Product to a specified named user. For clarification, the Licensed Product can be installed on multiple systems, but only the named user may access the Licensed Product on any one system at any given time. Use of the Licensed Product is further restricted to use on the Application(s) stated in the applicable Purchasing Agreement.
III. Scan License
A “Scan License” restricts the use of the Licensed Product to the number of scans identified in the applicable Purchasing Agreement. Use of the Licensed Product is further restricted to use on the Application(s) stated in the applicable Purchasing Agreement.
IV. Unlimited Scan License
An “Unlimited Scan License” restricts the use of the Licensed Product to an unlimited number of scans on the Application(s) identified in the applicable Purchasing Agreement.
*For purposes of types III and IV, above, a “scan” means the completion of one analysis cycle by the Licensed Product.
**An “Application” is the Code Base or Project identified in the applicable Purchasing Agreement.
— For Black Duck Licensed Products —
I. “Application” – (legacy as of November 1, 2020) means the software code associated with a single software build, including multiple versions thereof.
II. “Code Contributor” – (legacy as of November 1, 2020) means the individuals within or contracted by the Customer’s organization who contribute or work with code for an Application that will be scanned or analyzed by the Licensed Product. The number of Code Contributors includes all developers, engineers, analysts, architects, testers and managers who have written, modified or reviewed code for any scanned or analyzed Application during the License Term, as well as any individuals who interact with the Licensed Product via UI, email/text alerts, API, or third-party integration. Code Contributors do not include, however, those individuals within the Customer’s organization who perform only software related documentation or project management tasks.
III. Team License – (current as of November 1, 2020)
A “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases (in some organizations this is referred to as applications or projects) being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold with a minimum size of 10.
A “Team Member” is an individual within the named development team.
IV. “Managed Code Base Capacity License” means a license based on the size of the code base owned or controlled by Customer that is input into the Licensed Product by Customer and managed using that Licensed Product over the course of the applicable license term. If applicable, the size of the managed code base equals the aggregate of code added to the managed code base; provided that the size of the managed code base does not include code used by Customer for training purposes or that is inadvertently added by Customer and deleted upon discovery.
- For Seeker Licensed Products –
I. “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases (in some organizations this is referred to as applications or projects) being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold with a minimum size of 10.
A “Team Member” is an individual within the named development team.
- For Intelligent Orchestration Licensed Products –
I. “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases (in some organizations this is referred to as applications or projects) being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold with a minimum size of 10.
A “Team Member” is an individual within the named development team.
- For eLearning Licensed Products –
I. "Named User" means an Authorized User identified by a customer to use the eLearning tool through a unique login account. Named Users must remain the same for a minimum of twelve (12) months and may be transferred to another Named User thereafter.
- For Code Dx Licensed Products –
I. “Asset” means, pertaining to the InfraSec capability, a network or infrastructure component, such as an IP address, that is monitored by the Code Dx system for the purposes of reporting on network vulnerabilities. Examples include network scan results from Nessus, and IP addresses.
II. “Project” means a project within the Code Dx system is defined as a software application or component(s) that is analyzed separately through Code Dx. Projects can be hierarchical with one or more components. Typically, projects are a group of files that make up the software application. A project is defined by the setup in Code Dx and not limited in size or other external parameters such as the delivered functionality or by means of its installation. Projects, once defined, are not reusable. Re-use constitutes another project by definition.
III. “User” means a ‘named user’ of the Code Dx system. A *named user is someone who would log into the Code Dx server UI to perform their job duties such as reviewing vulnerability findings, assigning status, configuration, dashboarding and more. The named user can be but is not limited to AppSec and DevOps team members, security and triage analysts and security leads (including developers). Some beneficiaries of Code Dx do not log directly into the system but benefit via interaction with the server via APIs and DevOps tools such as JIRA, Jenkins, etc. These beneficiaries do not require a user license. Only those users that log into the UI require a user license.
*To accommodate team changes, such as an internal job role change, a team member leaving the organization, etc., by agreement, named users can be changed on a quarterly basis within the Code Dx system.
IV. “Team License” restricts use of the Licensed Product within a named development team. The team is licensed to access the Licensed Product based upon the total number of individuals in the team, and the Code Bases (in some organizations this is referred to as applications or projects) being developed by various members of the team. Once the team name, team size, and Code Bases are established, anyone within that team is authorized to access the Licensed Product during the License Term. If the team grows beyond its original size, additional license increments must be purchased to keep the entire team licensed. The size of the team must include all contractors that require access to the Licensed Product. All Team Licenses are sold with a minimum size of 10.
A “Team Member” is an individual within the named development team.