Common use of Common Security Configurations Clause in Contracts

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 vendor 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 The vendor 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 vendor shall maintain certify that operability is maintained with evolving FDCC standards standards. A Common Security Configuration Certification shall be submitted to the SPM and PCO in electronic format, or as they evolveotherwise requested by the SPM, upon request.