Operational Security Mode Sample Clauses

Operational Security Mode. [If both parties use the concept of Protection Levels and Levels-of-Concern for Confidentiality, Integrity, and Availability based upon their implementation common criteria, then enter the values for each as documented for both systems. Optionally, the security mode of operations could be documented for both systems.]
Sample 1
AutoNDA by SimpleDocs
Operational Security Mode. EGS System Categorization Level: The system categorization level for EGS is MODERATE as noted in the system’s system security plan is as follows: CATEGORIZATION LEVEL FOR CIA HIGH MODERATE LOW Confidentiality: X Integrity: X Availability: X EGS received its’ most recent Authorization to Operate on <<INSERT CURRENT ATO DATE>> <<VENDOR SYSTEM>> System Categorization Level: The system categorization level for <<VENDOR SYSTEM>> is <<INSERT VENDOR SYSTEM CATEGORY>> as noted in the system’s system security plan is as follows: CATEGORIZATION LEVEL FOR CIA HIGH MODERATE LOW Confidentiality: Integrity: Availability:
Sample 1
Operational Security Mode. The table below lists the Federal Information Processing Standard (FIPS 199) security categorization for the SBA system(s) in Table 2-1.] Table 5-1: System Sensitivity Levels Security Objective Level of Risk High Medium Low Confidentiality X Integrity X Availability X
Sample 1

Related to Operational Security Mode

  • Additional security requirements The following provisions apply in respect of any Additional Security provided:

  • Additional Security This guarantee is in addition to and is not in any way prejudiced by any other guarantee or security now or subsequently held by any Finance Party.

  • Technical Security Controls 35 a. Workstation/Laptop encryption. All workstations and laptops that store PHI COUNTY 36 discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of 37 COUNTY either directly or temporarily must be encrypted using a FIPS 140-2 certified algorithm which 1 is 128bit or higher, such as AES. The encryption solution must be full disk unless approved by the 2 COUNTY.

  • NATIONAL SECURITY Nothing in this Agreement shall be construed:

  • Additional Service Characteristics 3.12 The technical specification of the Bitstream 2a Service is set out in Appendix B.

  • Organizational Security 2.1.1 It is the mutual intention of the parties that the provisions of this Article protect the rights of individual workers without restricting CSEA’s rights.

  • Operational Support Systems (OSS 2.13.1 BellSouth has developed and made available the following electronic interfaces by which <<customer_name>> may submit LSRs electronically. LENS Local Exchange Navigation System EDI Electronic Data Interchange TAG Telecommunications Access Gateway

  • Operational Support Systems <<customer_name>> shall pay charges for Operational Support Systems (OSS) as set forth in this Agreement in Attachment 1 and/or in Attachments 2, 3 and 5, as applicable.

  • Contractor Security Clearance Customers may designate certain duties and/or positions as positions of “special trust” because they involve special trust responsibilities, are located in sensitive locations, or have key capabilities with access to sensitive or confidential information. The designation of a special trust position or duties is at the sole discretion of the Customer. Contractor or Contractor’s employees and Staff who, in the performance of this Contract, will be assigned to work in positions determined by the Customer to be positions of special trust, may be required to submit to background screening and be approved by the Customer to work on this Contract.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

Time is Money Join Law Insider Premium to draft better contracts faster.