Common Security Configurations Sample Clauses

Common Security Configurations. The provider of information technology shall certify applications are fully functional and operate correctly as intended on systems using the Federal Desktop Core Configuration (FDCC). This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista). For the Windows XP settings, see: xxxx://xxxx.xxxx.xxx/itsec/guidance_WinXP.html, and for the Windows Vista settings, see: xxxx://xxxx.xxxx.xxx/itsec/guidance_vista.html. The standard software installation, operation, maintenance, update, and/or patching processes shall not alter the approved FDCC configuration settings. The information technology provider should also use the Windows Installer Service for installation to the default “program files” directory and should be able to silently install and uninstall. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.
AutoNDA by SimpleDocs
Common Security Configurations. The provider of information technology shall certify applications are fully functional and operate correctly as intended on systems using the Federal Desktop Core Configuration (FDCC). This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista). For the Windows XP settings, see: xxxx://xxxx.xxxx.xxx/itsec/guidance_WinXP.html, and for the Windows Vista settings, see: xxxx://xxxx.xxxx.xxx/itsec/guidance_vista.html. The standard installation, operation, maintenance, updates, and/or patching of software shall not alter the configuration settings from the approved FDCC configuration. The information technology should also use an installer service for installation to the default "program files" directory and should be able to silently install and uninstall. Applications designed for normal end users shall run in the standard user context without elevated system administration privileges. Publisher shall also certify that any subsequent product/module for the life of the agreement is/are fully functional and operate correctly as intended on systems using Federal Desktop Core Configuration (FDCC) prior to any product/module revisions being made available for Government use. Further, the Publisher shall maintain operability with FDCC standards as they evolve.
Common Security Configurations. The provider of information technology (IT), at no additional cost to the Government, shall ensure applications are fully functional and operate correctly as intended on systems using the Federal Desktop Core Configuration (FDCC). The FDCC includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista). IAW OMB memorandum M- 07-18, “Ensuring New Acquisitions Include Common Security Configurations,” a virtual machine has been established to provide IT providers access to FDCC Windows XP and Vista images. These virtual machine images can be found at: xxxx://xxxx.xxxx.xxx/fdcc. The National Institute of Standards and Technology (NIST) also established a Security Content Automation Protocol (S-CAP) to help IT providers make self- assessments of their products. IT providers must use S-CAP validated tools, as they become available, to certify their products do not alter the virtual machine configurations. Links to the S-CAP tools, and additional information about the S-CAP process can be found at: xxxx://xxx.xxxx.xxx/scap.cfm

Related to Common Security Configurations

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Security Cameras Security cameras have been installed throughout the Facility; however, they will not routinely be used in areas where there is an expectation of privacy, such as restrooms or patient care areas.

  • Interconnection Facilities Engineering Procurement and Construction Interconnection Facilities, Network Upgrades, and Distribution Upgrades shall be studied, designed, and constructed pursuant to Good Utility Practice. Such studies, design and construction shall be based on the assumed accuracy and completeness of all technical information received by the Participating TO and the CAISO from the Interconnection Customer associated with interconnecting the Large Generating Facility.

  • AIRCRAFT CONFIGURATION The guarantees defined in Paragraphs 2 and 3 below (the “Guarantees”) are applicable to the A321 Aircraft as described in the A321 Standard Specification ***** as amended by the following SCNs:

  • SECURITY CODES If the Custodian issues to the Company security codes, passwords or test keys in order that it may verify that certain transmissions of information, including Proper Instructions, have been originated by the Company, the Company shall take all commercially reasonable steps to safeguard any security codes, passwords, test keys or other security devices which the Custodian shall make available.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Tooling Unless otherwise specified in this Agreement, all tooling and/or all other articles required for the performance hereof shall be furnished by Seller, maintained in good condition and replaced when necessary at Seller's expense. If NETAPP agrees to pay Seller for special tooling or other items either separately or as a stated part of the unit price of Goods purchased herein, title to same shall be and remain in NETAPP upon payment therefore.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • 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.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

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