GRC Solutions PWS (NEW) - Veterans Affairs



PERFORMANCE WORK STATEMENT (PWS)DEPARTMENT OF VETERANS AFFAIRSOFFICE OF INFORMATION TECHNOLOGY (OIT)OFFICE OF INFORMATION SECURITY (OIS)OFFICE OF CYBER SECURITY (OCS) andRISK MANAGEMENT & INCIDENT RESPONSE (RMIR)GOVERNANCE RISK and COMPLIANCE (GRC) SOLUTION for VA’sINFORMATION SECURITY CONTINUOUS MONITORING and RISK MANAGEMENT PROGRAMSDate: 07/6/2012TAC-12-05073PWS Version Number: 0.24 Contents TOC \o "1-3" \h \z \u 1.0BACKGROUND PAGEREF _Toc329242717 \h 42.0APPLICABLE DOCUMENTS PAGEREF _Toc329242718 \h 92.1 Other VA Initiatives or supporting systems PAGEREF _Toc329242719 \h 113.0SCOPE OF WORK PAGEREF _Toc329242720 \h 114.0PERFORMANCE DETAILS PAGEREF _Toc329242721 \h 134.1PERFORMANCE PERIOD PAGEREF _Toc329242722 \h 134.2PLACE OF PERFORMANCE PAGEREF _Toc329242723 \h 134.3TRAVEL PAGEREF _Toc329242724 \h 145.0SPECIFIC TASKS AND DELIVERABLES PAGEREF _Toc329242725 \h 145.1PROJECT MANAGEMENT PAGEREF _Toc329242726 \h 195.1.1CONTRACTOR PROJECT MANAGEMENT PLAN PAGEREF _Toc329242727 \h 195.1.2REPORTING REQUIREMENTS PAGEREF _Toc329242728 \h 195.2KICK-OFF MEETING PAGEREF _Toc329242729 \h 205.3PROJECT MANAGEMENT ACCOUNTABILITY SYSTEM (PMAS) SUPPORT PAGEREF _Toc329242730 \h 215.4TASK 1: SPECIFIC GRC SOLUTION REQUIREMENTS PAGEREF _Toc329242731 \h 215.4.1TASK TWO: SPECIFIC GRC SOLUTION REQUIREMENTS FOR VA INTEGRATION PAGEREF _Toc329242732 \h 245.4.2TASK THREE – IMPLEMENTATION SUPPORT SERVICES PAGEREF _Toc329242733 \h 275.4.3TASK FOUR - SYSTEM DESIGN & ENGINNERING PAGEREF _Toc329242734 \h 295.4.4TASK FIVE - SYSTEM AVAILABILITY PAGEREF _Toc329242735 \h 305.4.5TASK SIX - MAINTENANCE AND TECHNICAL SUPPORT PAGEREF _Toc329242736 \h 305.4.6TASK SEVEN - TRAINING PAGEREF _Toc329242737 \h 315.4.7OPTIONAL PERIOD 1: PAGEREF _Toc329242738 \h 325.4.8OPTIONAL PERIOD 2: PAGEREF _Toc329242739 \h 335.4.9OPTIONAL PERIOD 3: PAGEREF _Toc329242740 \h 355.4.10OPTIONAL PERIOD 4: PAGEREF _Toc329242741 \h 376.0GENERAL REQUIREMENTS PAGEREF _Toc329242742 \h 386.1ENTERPRISE AND IT FRAMEWORK PAGEREF _Toc329242743 \h 396.2POSITION/TASK RISK DESIGNATION LEVEL(S) AND CONTRACTOR PERSONNEL SECURITY REQUIREMENTS PAGEREF _Toc329242744 \h 406.2.1LOW RISK DESIGNATION TASKS PAGEREF _Toc329242745 \h 416.2.2MODERATE RISK DESIGNATION TASKS PAGEREF _Toc329242746 \h 416.2.3HIGH RISK DESIGNATION TASKS PAGEREF _Toc329242747 \h 416.2.4CONTRACTOR PERSONNEL SECURITY REQUIREMENTS PAGEREF _Toc329242748 \h 416.3METHOD AND DISTRIBUTION OF DELIVERABLES PAGEREF _Toc329242749 \h 426.4PERFORMANCE METRICS PAGEREF _Toc329242750 \h 436.5FACILITY/RESOURCE PROVISIONS PAGEREF _Toc329242751 \h 446.6GOVERNMENT FURNISHED PROPERTY PAGEREF _Toc329242752 \h 45ADDENDUM A (Cyber and Information Security Requirements) PAGEREF _Toc329242753 \h 46ADDENDUM B (6500.6, APPENDIX C, APPLICABLE PARAGRAPHS) PAGEREF _Toc329242754 \h 51ADDENDUM C (RFI QUESTIONS) PAGEREF _Toc329242755 \h 63ADDENDUM D (Acronym List) PAGEREF _Toc329242756 \h 66ADDENDUM E (ISCM CONOPS -- Data Flow and Security Architecture) PAGEREF _Toc329242757 \h 66ADDENDUM F (GRC Solution Requirements Spreadsheet) PAGEREF _Toc329242758 \h 66ADDENDUM G (Risk Management CONOPS Overview DRAFT) PAGEREF _Toc329242759 \h 66 BACKGROUNDThe Department of Veterans Affairs (VA) has three primary missions to the veteran: provide health care services to eligible Veterans Administered by the Veterans Health Administration (VHA); provide financial benefits to eligible veterans Administered by the Veteran Benefits Administration (VBA); and, provide burial services to eligible veterans Administered by the National Cemetery Administration (NCA). As part of its mission VA’s Office of Information Technology (OIT), Office of Information Security (OIS), Office of Policy, Privacy and Incident Response is to provide high quality, effective, and efficient Information Technology (IT) services to those responsible for providing care to the Veterans at the point-of-care as well as throughout all the points of the Veterans’ care and benefits in an effective, timely and secure manner.? VA depends on Information Management/Information Technology (IM/IT) systems to protect sensitive data to include that of Veterans, their dependents, and staff as well as data that is sensitive to VA operations to include data classified as confidential and/or classified. VA must comply with Office of Management and Budget (OMB) mandates, Public Law, Health and Human Services (HHS) requirements (e.g. Health Insurance Portability Act (HIPAA), Health Information Technology for Economic and Clinical Health (HITECH) Act), Department of Homeland Security (DHS) and National Institute of Standards and Technology (NIST) Guidance for Federal Information Security Management Act (FISMA) reporting, and Risk Management Framework (RMF) development. To meet current and future requirements in these areas the VA is evolving its posture to one of Continuous Monitoring (CM). NIST Interagency Report (IR), NISTIR-7756, states that “continuous monitoring is [the] ongoing observance with intent to provide warning. “A continuous monitoring capability is the ongoing observance and analysis of the operational states of systems to provide decision support regarding situational awareness and deviations from expectations” (p. 9). NISTIR-7756 additionally states that “CM supports both Cybersecurity and IT management domains. CM is now defined in the context of security risk management using the NIST Special Publication (SP) 800-137 definition: Information security CM is defined as “maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions” (p. 9).These enhanced CM capabilities for improved organizational risk management decisions is important for our Veterans, employees, and partnering government agencies, such as the Department of Defense (DoD). As an example of this is where VA has joint facilities and data sharing with the DOD, so insuring VA systems are secure and can be reported as such to another federal agency is critically important. Additionally, VA has embarked on the development of an Agency wide Risk Management (RM) program, which the proposed Governance, Risk, and Compliance (GRC) Solution, its data and presentation output and follow-on big data correlated analysis will provide a great resource for RM planning and mitigation.The GRC Solution is expected to leverage current VA information security programs in order to provide a CM / risk management solution as defined by NIST guidance. The GRC Solution will leverage assess management capabilities of SecureVA and National Security Operations Center (NSOC) network and asset management to support CM requirements. In addition, during times of data breaches, exploits, system vulnerabilities, and systems integrity verification it is important to insure that GRC is effectively integrated, expediently reported, incorporated into enterprise workflows and data warehouses to support trending reporting. This is important for management so they can make more nimble and decisive decisions. Following NIST guidance, automation, standardization and centralization is required to manage risk given the complexity of IT platforms. In OIT, current processes and capabilities are becoming outdated and cannot effectively recognize, in a coordinated and correlated fashion, the plethora of risk events, security posture changes, cyber incidents, data breaches, compliance audits, and associated and required scans and data collection monitoring. The current systems produce lots of meaningful data, uses several data silos and data is not standardized to support common reporting schemes, much less correlated for multidimensional risk analysis and recommendations. Some VA entities depend on elements of different data streams, but over time this can be prone to false analysis and scoring due to the lack of commercially supported systems calculators, risk scoring methodology, FISMA reporting requirements, and other critical functions which are flexible and changing requirements over time. The change in metrics, characteristics of systems, and legal’s requirements create challenges to conducting security audits. VA must continue to comply with FISMA, Title III of the E-Government Act of 2002. FISMA requires VA to develop, document, and implement an agency-wide program to provide information security for the information and information systems that support the operations and assets of the agency, including those provided or managed by another agency, contractor, or other source. FISMA requires agency officials, chief information officers (CIOs), and inspectors general (IGs) to conduct annual reviews of VA’s information security program and report the results to OMB Circular A-130 Management of Federal Information Resources. Information security management has been further enhanced by OMB with additional CM requirements and mandated reporting and standards practices assigned to DHS OMB’s Circular A-130, establishes policy and guidance on information technology management. It requires all VA information systems to have security plans and all systems to have formal emergency response capabilities; Federal Management and Fiscal Integrity Act reports to Congress be made in regards to the security of the systems; and that regular reviews and improvements of contingency plans for the systems be conducted. The recent changes in laws and guidance require the transformation of Certification and Accreditation (C&A) to an automated process called Assessment and Authorization (A&A) and guidance directs agencies to implement automation of the management of information in order to support guidance. VA’s current mechanism to manage C&A processes called “SMART” tool meets the above requirements of C&A by maintaining VA’s inventory of all FISMA reportable systems and reporting of, by monitoring the categorization of all information and information systems according to risk levels; all systems’ security controls; systems’ risk assessments; systems’ security plans; systems’ certification and accreditation; and CM?of systems’ security controls. The SMART tools were not designed to meet A&A needs, the GRC solution must support the VA’s automation requirements and re-engineering of C&A processes to an A&A capability. The objective of acquiring the GRC Solution is to deploy an effective enterprise wide CM capability for enhanced decision making from improved organizational risk management. The GRC Solution being sought should be made-up of existing set of software based systems which will provide the functionality and requirements of an Information Security Continuous Monitoring (ISCM) capability as described in NIST SP 800-137 for Federal Information Systems. The capabilities of this platform include a centralized data clearing house that enables the entire IT enterprise to be managed in terms of assets, risks and vulnerabilities. The features and functionality support workflow automation and knowledge management enabling all tiers of management to manage IT risk in a proactive, defined and consistent manner.The elements of which will be data connectors to legacy systems, A&A/FISMA/Authority to Operate (ATO) data inventory manager, Compliance manager, Risk Analysis engine, Presentation (Dashboard) engine, a near-real-time Actionable Risk Intelligence (ARI) Engine, and a Big Data correlated risk analysis capability (e.g. Data Warehouse analytics, Hadoop, etc) for predictive risk analysis, among others. Additionally, the core system will handle data input for FISMA and RM related activities as part of VA’s new ISCM program which is critically important to VA’s compliance, risk reduction, effective resource allocations, VA, and improved ability to operate at a higher tempo due to intelligent Risk reductions. The key initiatives and objectives of the GRC Solution is the establishment of an enterprise wide ISCM program and an enterprise wide information security (IS) and Privacy Risk Management program for enhanced organizational risk management decision making capabilities. The ISCM program needs to include: Asset Awareness, Threat Management, (e.g. NIST National Vulnerability Database(NVD)), Data Warehousing and real-time reporting, presentation and analysis. In accordance with the requirements for ISCM, which includes FISMA, CyberScope, DHS, NIST, and VA as defined in the next paragraph and in Applicable Documents listed in paragraph 2.0. The Information Security and Privacy Risk Management program will also include support for: HHS HIPAA and HITECH Acts by incorporating management of sensitive systems into and enterprise management capability in accordance with laws and guidance.OIS is responsible for developing, implementing, and maintaining an ISCM and Information Security and Privacy Risk Management programs across the VA enterprise. In addition, OIS is responsible for expanding its current IS and Privacy Risk Management to a more expansive automated agency wide program. In order to meet the goals and objectives of this task, the Office of Policy, Privacy and Incident Response in OIS established a centralized enterprise IT framework to support ISCM and RM requirements, guidance and laws. The structure is built around the NIST RMF and DHS’ Continuous Asset Evaluation, Situational Awareness and Risk Scoring (CAESARS) Reference Architecture (RA). VA ISCM framework provides for a robust Continuous Monitoring and Risk Management (CMRM) capability. VA’s CMRM is based on NIST SP 800-137, NIST IR 7756, Second Draft and guidance from the DHS, and the Department of State (DOS) sponsored Continuous Monitoring Work Group (CMWG) activities. Figure 1, below, provides a high level overview of VA’s architected ISCM data and process workflows that merge enterprise wide Cyber Security events, artifacts, policies and procedures into a lifecycle constant improvement model to support organizational risk management decisionsGOALSThe goals for the GRC Solution is to have the capability to enable VA to meet A&A requirements and automation of risk management workflows, the demands of the business, laws, policy, and requirements while operating within a defined and known Cyber Security risk posture. The tool should assist in the implementation of efficiencies and support the streamlining of many tasks including Systems Development Life Cycle (SDLC) project related activities. By centralizing SDLC artifacts and enabling access to this data, traditional organizational boundaries are broken down. The breaking down of organizational SDLC boundaries is going to be increasingly important as shared and enterprise centric IT data services are incorporated into the SDLC. Last but not least, the Tool should incorporate near-real-time Cyber Security data and events. The near-real-time nature of this capability supports Risk Management in developing ARI for quick and decisive executive action to reduce risk to systems and or facilities. The GRC Solution needs to integrate with all existing system tools and scanners to provide the greatest number of continuous reporting of 800-53 technical controls for CM, C&A/A&A, Risk Management scoring through a Common Vulnerability Scoring System (CVSS) calculator for near-real-time analysis and risk scoring and trending for display onto multilayered and correlated risk dashboards. The GRC Solution should provide analysis and risk scoring with multidimensional-correlated risk calculations using many available models as selected, at any time by a risk analyst and/or by management to include the NIST CVSS scoring engine. The correlated risk data will display onto multi-layered graphic dashboard displays, which will show the risk scoring and trending in total and break down by region, state (& others); by facility and system and easily integrate into a Risk layer of the existing geoVA graphical GIS dashboard. Additionally, the correlated Analysis/Risk Scoring Subsystem (A/RSS) should provide near-real-time ARI. GRC Solution Goals and Objectives:Leverage existing and emerging VA systems including those that support Cyber Security, Risk Management, Operations, and Helpdesk activities. Reduce VA’s Cyber Security Risk Posture and enable the VA to operate within a known and defined Cyber Security Risk Posture. Streamlines SDLC activities and automation of C&A workflow to A&A workflow reducing Cyber Security impacts on project managers Effectively manage VA’s IT platforms in near real-time and respond in known and identified ways to Cyber Security threats Centralize Cyber Security data artifacts to be available for use by the enterprise and all management staff tiers Supports situational awareness by integrating asset awareness data with real-time vulnerability data Incorporate real-time vulnerability data with VA’s operational data and IT knowledge base (baselined systems) to support more informed IT decisions Provide a RMF, standardizing analysis and support management of Cyber Security risk posture. Standardize Risk Scoring activities / normalizes data for Risk Scoring with, among other things a multidimensional dynamic and effectively adjustable A/RSS which provides near-real-time and trending data by system, facility, region, and other recognized geographic and organizational reporting boundariesMeet OMB CyberScope reporting requirements, data is available and normalized for reporting purposes Leverage VAs current reporting and auditing system functions from IBM Cognos software Support data services provided by the Asset Awareness Subsystem functions utilizing BigFix and other Cyber Security tools noted in ISCM Concept of Operations (CONOPS) Leverage VA’s Enterprise Management Framework (EMF) work stream to support Database Subsystem and Data Warehouse functions Identify, document and trend gaps between audit findings from multiple sources within the oversight communityIntegration of audit findings to remediation efforts, Department-wideQuick and seamless integration across VA’s IT enterpriseModulation capabilities to deliver solutions faster while tailoring for specific VA needsFunctions that allow discovery of assets based on various operating platforms and environmentsLayered approach to vulnerability identification (application control, change control, server, etc.)Risk Assessment (RA) and System Security Plan (SSP) development, output, and storage.Plan of Actions & Milestones (POA&M) generation, storage, and reference use as part of ISCM.APPLICABLE DOCUMENTSDocuments referenced or germane to this Performance Work Statement (PWS) are listed below. In the performance of the tasks associated with this Performance Work Statement, the Contractor shall comply with the following:44 U.S.C. § 3541,?“Federal Information Security Management Act (FISMA) of 2002”Federal Information Processing Standards (FIPS) Publication 140-2, “Security Requirements For Cryptographic Modules”FIPS Pub 201, “Personal Identity Verification of Federal Employees and Contractors,” March 200610 U.S.C. § 2224, "Defense Information Assurance Program"Software Engineering Institute, Software Acquisition Capability Maturity Modeling (SA CMM) Level 2 procedures and processes5 U.S.C. § 552a, as amended, “The Privacy Act of 1974” 42 U.S.C. § 2000d “Title VI of the Civil Rights Act of 1964”Department of Veterans Affairs (VA) Directive 0710, “Personnel Suitability and Security Program,” May 18, 2007VA Directive 6102, “Internet/Intranet Services,” July 15, 200836 C.F.R. Part 1194 “Electronic and Information Technology Accessibility Standards,” July 1, 2003OMB Circular A-130, “Management of Federal Information Resources,” November 28, 200032 C.F.R. Part 199, “Civilian Health and Medical Program of the Uniformed Services (CHAMPUS)”An Introductory Resource Guide for Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule, October 2008Sections 504 and 508 of the Rehabilitation Act (29 U.S.C. § 794d), as amended by the Workforce Investment Act of 1998 (P.L. 105-220), August 7, 1998Homeland Security Presidential Directive (12) (HSPD-12), August 27, 2004VA Directive 6500, “Information Security Program,” August 4, 2006VA Handbook 6500, “Information Security Program,” September 18, 2007VA Handbook 6500.1, “Electronic Media Sanitization,” March 22, 2010VA Handbook 6500.2, “Management of Security and Privacy Incidents,” June 17, 2008.VA Handbook 6500.3, “Certification and Accreditation of VA Information Systems,” November 24, 2008.VA Handbook, 6500.5, Incorporating Security and Privacy in System Development Lifecycle.VA Handbook 6500.6, “Contract Security,” March 12, 2010Project Management Accountability System (PMAS) portal (reference PWS References -Technical Library at )OIT ProPath Process Methodology (reference PWS References -Technical Library and ProPath Library links at ) NOTE: In the event of a conflict, OIT ProPath takes precedence over other processes or methodologies. Technical Reference Model (TRM) (reference at )National Institute Standards and Technology (NIST) Special PublicationsVA Directive 6508, VA Privacy Impact Assessment, October 3, 2008VA Directive 6300, Records and Information Management, February 26, 2009VA Handbook, 6300.1, Records Management Procedures, March 24, 2010OMB Circular A-130, Appendix III Security commensurate with the risk and the magnitude of harm resulting from the loss, misuse, or unauthorized access to or modification of information. OMB M-10-15, FY 2010 Reporting Instructions for the Federal Information Security Management Act and Agency Privacy Management. The requires agencies to continuously monitor security-related information from across the enterprise in a manageable and actionable way OMB M-11-33 – Monthly CyberScope Reporting NIST IR 7756, CAESARS Framework Extension: An Enterprise Continuous Monitoring Technical Reference Architecture (Second Draft) NIST SP 800-137 Draft Information Security Continuous Monitoring for Federal Information Systems and Organizations NIST SP 800-39, DRAFT Integrated Enterprise-Wide Risk Management: Organization, Mission, and Information System View NIST SP 800-37, Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach NIST SP 800-53, Revision 3, Recommended Security Controls for Federal Information Systems and Organizations NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems: Building Effective Security Assessment Plans NIST SP 800-55, rev. 1, Performance Measurement Guide for Information SecurityNIST SP 800-126, Revision 1, DRAFT, The Technical Specification for the Security Content Automation Protocol (SCAP): NIST 800-128, DRAFT, Guide for Security Configuration Management of Information SystemsProject Management Accountability System (PMAS) portal (reference PWS References -Technical Library at )VA Handbook, 6300.1, Records Management Procedures, March 24, 2010 CNSSI-1253 defined security categories, classification, organizations, business functions, program, and system type.VA Security Management And Reporting Tool (SMART) Functional Requirements Document, v 1.0Project Management Institute’s (PMI?) Project Management Body of Knowledge (PMBOK)2.1 Other VA Initiatives or supporting systemsInitiatives or systems that the GRC Solution is expected to leverage, interface with in order to support the VA’s enterprise ISCM and RM requirements. SecureVA – Asset Management of VA endpoints.Enterprise Management Framework Remedy Ticketing System and CA UnicenterNSOC – NESSUS and Network Management servicesInformation Security Continuous Monitoring CONOPS Information Security Risk Management CONOPS (DRAFT)SCOPE OF WORKThe Contractor shall provide all resources necessary to accomplish tasks as described in this Performance Work Statement (PWS). The Contractor shall provide support for a turn-key, custom configured, commercial-off-the-shelf (COTS) based, enterprise-wide, integrated GRC Solution which will function as a key component and primary core for VA’s ISCM. The solution must integrate with existing VA systems (sensors, probes, software, and similar) to provide ISCM abilities. The GRC Solution must provide the needs of VA’s IS and Privacy Risk Management programs across the enterprise in accordance with NIST SP 800-137, NIST IR 7756, 2nd Draft, guidance from the DHS, and the DoS sponsored CMWG activities and as added to in this PWS for a continuous lifecycle improvement model. The GRC Solution shall provide the architectures identified in the VA’s ISCM CONOPS including: (1) an A/RSS for standardized risk modeling and multidimensional correlated risk analytics; (2) a Presentation/Reporting Subsystem (P/RSS) for the output of multilayered and easily configurable dashboards, which can be provided to many level of operation personnel and management, as well as be integrated into multiple presentation layers of VA’s geoVA dashboard; (3) Database Sub-Systems (DBSS) designed the ingestion, storage and retrieval for analytics, (4) a Sensor Subsystem (SSS) for integration and data collection of all VA data sources from scans, sensors, probes, and similar; (5) an Inventory Subsystem (ISS) that contains all request documentation sources for FISMA, A&A, ATO, (e.g.- Risk Assessments, SSPs, Plans of Actions and Milestones (POA&M), etc), and (6) Big Data analytics with specialized applications (e.g. Hadoop) for deep multi-vector, multidimensional correlation analysis for vulnerability discovery, rescoring known vulnerabilities, and the development of a near-real-time ARI analysis and reporting capability. The COTS GRC shall provide a means for VA to fully develop and implement an agency-wide risk management governance structure and strategy for all IS related activities, systems, and functions, as well as for data and privacy breach risks and compliance. The standard reference for VA’s requirements come from NIST SP: (1) SP 800-137: ISCM for Federal Information Systems and Organizations; (2) SP 800-39: Managing Information Security Risk; (3) SP 800-37: Guide for Applying the Risk Management Framework to Federal Information Systems; (4) NISTIR-7756: CAESARS Framework Extension: An Enterprise Continuous Monitoring Technical Reference Model (Second Draft), and (5) OMB Memorandum: OMB-M-11-33: CyberScope reporting.VA’s plan is to have an enhanced organizational risk management decision making capabilities by combining our current ISCM efforts and outputs with an established, highly available, COTS GRC Solution to advance VA’s ability to reduce risk to its lowest possible level, while maintaining the highest operational tempo possible. The GRC Solution shall provide knowledge management workflow automation and decision making support as part of re-engineering the VA’s Information Security management practices from a Certification and Accreditation capability to an ongoing, near-real time Assessment and Authorization capability.The GRC Solution shall integrate with VA’s existing systems and tools that are being utilized for VA’s current ISCM program. The planned GRC Solution is critically important to VA, due to the complexity of the VA system and network, as well public law and mandates which VA is required to follow. Some of these complexities and requirements of VA’s systems and law which must be accounted for include:Over 1,500 facilities located in all 50 states, some US territories, Guam, Puerto Rico, and the Philippines,Over 1,000,000 data collection points, Over 600 discrete and vast systems, many of which exist to satisfy laws and regulatory requirements,The fact that VA’s enterprise has the second most complex infrastructure in the federal government,Much of VA’s data is confidential due to large volumes of Personal Identification Information (PII) and Protected Health Information (PHI), as well as confidential and or classified information for VA’s continuity plans or other areas.Critically required FISMA accreditation and compliance for system, reauthorizations so new a Authority to Operate (ATO) can be approved by VA’s CIO,Compliance with several laws and regulations to include, but not limited to: Public Law 104-191 -- HIPAA 1996 (HIPAA); The Privacy Act of 1974, 5 U.S.C. § 552a, As Amended; Title III, Pub. L. No. 107-347 -- Federal Information Security Management Act of 2002 (FISMA), As Amended; and other laws and regulations which VA must comply with and that the GRC Solution is integral to the ISCM systems success at meeting these requirements,Agency wide information security and privacy risk management requirements,Critical cyber vulnerability reporting, trending, and mitigation,OMB mandated CyberScope reporting to DHS, Executive dashboard development and population to key VA executives to include the Secretary of the Department of Veterans Affairs (SECVA), such dashboards must integrate into the geoVA Dashboard.Multilayered dashboard requirements for subsets of users, by position and area of responsibility,Data The overall Data warehouse services include functionality to manage the assets, data artifacts and user community as described in this document and the attached ISCM CONOPS,All other applicable laws, regulations, policies, and procedures which VA follows.Due to these complexities and requirements, which VA has and is required to adhere to, VA requires a vendor that has experience successfully deploying, implementing, integrating, and custom configuring their proposed GRC Solution as part of another large Federal Government agency’s ISCM and Risk Management program. The Contractor shall provide all resources (e.g. - personnel, software, training, etc) necessary to accomplish the implementation of a GRC Solution, based on modified and custom configured suite of COTS software, application modules, software connectors, implementation plans, and integration plans under the guidance of VA. Additionally Contractor must provide a series of different types of training, as provided and detailed in this PWS. The solution shall include a detailed agile implementation and integration plan, with testing, maintenance, 24x7x365 help desk support, and training required for use, modification and Administration of the GRC Solution. PERFORMANCE DETAILSPERFORMANCE PERIODThe period of performance shall be one 12-month base period with four 12-month option periods. PLACE OF PERFORMANCETasks under this PWS shall be performed at the Contractor's facilities. Work may be performed at remote locations with prior approval of the Contracting Officer’s Representative (COR). TRAVELThe Government anticipates travel under this effort to perform the tasks associated with the effort, as well as to attend program-related meetings or conferences through the period of performance.?Include all estimated travel costs in your firm-fixed price line items. These costs will not be directly reimbursed by the Government.The total estimated number of trips in support of the program related meetings for this effort should not exceed 42 trips per year and not exceed $84,000 for each period of performance.?Anticipated locations include the following, estimated at 4-5 days per trip in duration:Washington, DC Metropolitan AreaAustin, TXMartinsburg, WVHines, ILOther travel associated with tasks and deliverables identified throughout section 5 of this PWS which are not deemed Government requested program related meetings must be included in Contractor’s pricing for those tasks and deliverables.SPECIFIC TASKS AND DELIVERABLESThe Contractor shall perform the following: Provide an A/RSS for multidimensional correlated risk analytics, and develop an associated A/RSS CONOPS which shall include the identification of dependent, independent, controlling, and intervening variables, algorithms, correlation models and Big Data schema and data mashing plans; Provide a P/RSS for multilayered dashboards and integration into multiple presentation layers for all levels of customers to include, but not limited to executives, managers, risk analyst, information security officers and privacy officers, and the development of an associated A/RSS CONOPS which shall include multilayered dashboards for different types of users from information security officers (ISO); Privacy Officers (PO); Facility, Regional, and Agency CIOs, Agency Chief Information Security Officers (CISO); Risk Analysts, A&A Analyst and program managers; and others. Customizable Graphic Dashboard which displays key performance indicators, data trends, risk scoring, and alerts. User Customizable Graphic Dashboard which displays key performance indicators, data trends, risk scoring, and alerts; Provide a (DBSS), capable of supporting the user community, assets as previously described and includes the ability to process and manage raw unprocessed data, de-conflicted data (redundant findings are removed) and processed data for specific data views. The DBSS shall provide a Data warehouse, with designs for all elements of the GRC Solution, and especially for data intensive risk correlation usage for near-real-time ARI for analysis and reporting;The data warehouse services are expected to support forensic requirements, ad-hock queries, pre-defined reports and dashboards. The data warehouse services are expected to include operational data, data marts and Online Analytical Processing (OLAP) structures. Due to the number of assets and events that need to be managed engineering designs that include clustered systems (e.g. Hadoop) may need to be employed for decrease storage requirements and faster access to data. The DBSS must be able to support the user community while maintaining access during routine and peak data loads. Processing includes de-confliction of data being obtained for storage and analysis in different formats from different sources. The “…purpose of the [DBSS] …is to serve as the central repository of all [GRC Solution] … data, including both raw data that is reported from the sensors on the individual platforms of the Sensor Subsystem (SSS) and data that is developed within the RC Solution A/RSS as a result of ‘cleansing’, pre-processing, analysis, and scoring processes. . . . [The GRC Solution database] also includes any tools that are required by the GRC Solution Database/Repository to perform data-pull operations from the Sensor Subsystem platforms.’ Of note is that the Database Subsystem encompasses the ‘repository of configuration baselines’ and thus it contains machine-readable descriptions of the required baseline security posture of the organization’s systems as well as data on known vulnerabilities and their severity (e.g., from the National Vulnerability Database [NVD]). It also encompasses a ‘repository of asset inventory baselines,’ although this asset inventory database is not described in much detail” (NISTIR-7756). The DBSS should also be capable of maintaining and accessing routine and peak data for storage and analysis in efficient formats to include Hadoop (or equivalent) for Big Data access and analysis in near-real-time;The GRC Solution must integrate with VA’s SecureVA capabilities to support a SSS as described in VA’s ISCM CONOPS. The SSS is currently being deployed to enable VA to manage assets. The feed from the SSS is expected to support GRC requirements for asset management. The GRC capability is expected to providing a centralized capability that support integration and data collection of various data sources from all current and future VA utilized sensors and scanners. The GRC Solution is further expected to support provide a SSS which allows the SSS to generate data from multiple tools, formats as needed to incorporate assets into ISCM RM workflows and further allowing the data feed sources to be enumerated and reported upon;Provide an ISS which shall maintain VA’s inventory of all FISMA reportable systems and reporting of, by monitoring the status (e.g. Assessment, Authorization, POA&M, Risk Posture) of all information and information systems according to risk levels; all systems’ security controls; systems’ risk assessments; systems’ security plans; systems’ certification and accreditation; and continuous monitoring?of systems’ security controls. This is required in order to meet FISMA requirements to develop, document, and implement an agency-wide program to provide information security for the information and information systems that support the operations and assets of the agency. This requires agency officials, CIOs, and IGs to conduct annual reviews of VA’s information security program and report the results to OMB. The OMB Circular A-130, Management of Federal Information Resources, requires that all VA information systems have security plans and that all systems have formal emergency response capabilities; Federal Management and Fiscal Integrity Act reports to Congress be made in regards to the security of the systems; and that regular reviews and improvements of contingency plans for the systems be conducted. The GRC Solution shall provide an ISS which continues to facilitate the requirements set forth by various federal laws such as FISMA, which sets specific performance reports requirements and data collection to meet guidelines established by OMB. The ISS will serve as VA’s central repository for all IT security deficiencies (aka POA&Ms) meets the above noted mandates and others, and serves to comply with reporting requirements for reports that are presented to OMB and Congressional committees throughout each fiscal year, in addition to OMB and DHS quarterly FISMA reporting requirements. Additionally, as part of the FISMA reporting process and maintenance of systems and POA&M inventory, the ISS will serve as the sole repository of all FISMA reportable systems inventory for VA. The ISS will support annual testing of security controls for CM and A&A process tracking to ensure project managers and business process owners have the tools necessary to appropriately manage IT security deficiencies as part of their project management methodology and for department wide A&A activity. Proposed ISS must provide at least 150 custom reports each of which operate as scheduled on daily, weekly, monthly, quarterly, semi-annual, and annual, basis as well as ad-hock queries, each of which may be set to be distributed to different sets of users. Reports must also have altering capabilities.The ISS should replace and improve current capabilities, for all artifacts for FISMA, A&A, and ATO processes to include, but limited to: Risk Assessments, SSPs, Continuity Plans, Remediation Plans and Actions taken, and POA&M.Provide a Big Data risk and correlation engine for near-real-time ARI for analysis and reporting and deep correlated analytics to reveal unknown vulnerabilities and to reclassify vulnerabilities and their level of criticality;Provide Comprehensive report templates for use by people across the agency for the development of: Risk Assessments, SSP, Continuity Plans, Remediation Plans and POA&M;Two-way Integration of all dashboards into the geoVA Dashboard (geoVA is a ArcGIS based graphic dashboard developed by VA which integrates many third party data feeds);Consolidated Threat & Vulnerability Management analysis, reporting (statistical and visual);FISMA reporting to DHS CyberScope;Perform Gap Analysis between current VA initiatives (e.g. SecureVA, Enterprise Management Framework) and GRC tool requirements, expectations.The GRC Solution will require VA specific software configuration and modification (i.e., customization) to support workflow processes that are unique to VA. The GRC Solution must be able to be integrated with other commercial products in use by VA’s information security program. VA’s ISCM and RM programs, with the use and functionality that the GRC Solution provides, will allow management, at all levels, to make more informed decisions with respect to Agency risk. This will be made possible via thoroughly correlated and comprehensive (multidimensional) risk based analytics and multi-tiered graphical displays (dashboards). The ISCM program and the GRC Solution should provide the capabilities, as called for in NIST SP 800-137 guidance and the NISTIR-7756 technical reference manual, and additional areas as is outlined in this PWS. As stated in NISTIR 7756, 2nd Draft, (see Section 2.0): To focus on Cybersecurity, we now redefine CM in the context of security risk management using the NIST SP 800-137 definition: ISCM is defined as “maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions” (p.9).110490323850Figure 1: Enterprise Architecture View of Continuous Monitoring(Adapted from NISTIR-7756, Second Draft, p. 11).The Contractor’s GRC Solution must clearly demonstrate how it will meet or exceed VA’s goal to fully develop and implement an agency-wide RM governance structure and strategy for all IS and Privacy protection related activities, systems, and functions, as well as for data breach and privacy breach risks and compliance. The standard reference for VA’s requirements is identified in Section 2.0, Applicable Documents, above. In the case where a requirement is not clearly met, the Contractor must clearly provide a list of capabilities and or requirements which they are not able to meet.VA’s plan is to combine current ISCM efforts, outputs, and architectures with an established, highly available, GRC Solution to advance VA’s ability to reduce risk to its lowest possible level, while maintaining the highest operational tempo possible. The combined architecture supports guidance ensuring that RMF data services are designed to support requirements, collaboration and organizational risk management needs. A risk based and balanced approach to these requirements include trending, multidimensional risk correlation, data and privacy incident scoring and trending, data processing from many different existing and future systems for analysis and risk scoring, and similar activities in order to provide a multifaceted risk profile by facility and systems, as well as agency, and ARI recommendations.The GRC Solution, as part of ISCM, must be able to automate the A&A program, and correlated multidimensional risk profiles, dashboards, and trending as part of more impactful and essential agency wide Risk Management program as establish by statute to be led by OIS. PROJECT MANAGEMENTCONTRACTOR PROJECT MANAGEMENT PLANThe Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of the contract. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, risks and resource support.?The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The initial baseline CPMP shall be concurred upon and updated monthly thereafter. The Contractor shall update and maintain the VA PM approved CPMP throughout the period of performance. The CPMP must be in compliance with Project Management professional standards, specifically Project Management Institute’s (PMI?) Project Management Body of Knowledge (PMBOK), and the VA OIT Project Management Guide. The CPMP shall be responsive to this PWS and describe the approach to be used for each aspect of the PWS. The Government anticipates that it will review the PMP quarterly during the base period of performance, and then annually for each option period exercised. Deliverables: Contractor Project Management PlanREPORTING REQUIREMENTSThe Contractor shall provide the COR with Weekly Progress Reports in electronic form in Microsoft Word and Project formats.?The report shall include detailed instructions/explanations for each required data element, to ensure that data is accurate and consistent. These reports shall reflect data as of the last day of the preceding Week.? The Weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period.?The report shall also identify any problems that arose and a description of how the problems were resolved.? If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the CPMP and report any deviations. It is expected that the Contractor will keep in communication with VA accordingly so that issues that arise are transparent to both parties to prevent escalation of outstanding issues. The Contractor shall provide:Summary description of activities and accomplishments during the report period; Monitor performance against the CPMP and report any deviations;Description of problems and issues encountered during the report period; Status of open problems or issues identified in previous report(s), risk assessment, and mitigation plan;Status of upcoming activities from Contractor generated schedule; andMonthly activity Gantt charts, to include task descriptions, task start and end dates, task completion information, dependencies, slack time, critical path, and milestones.Deliverables:? Weekly Progress ReportKICK-OFF MEETINGThe Contractor shall conduct an onsite Kick-Off Meeting within ten (10) business days of award at 1100 First St, NE, Washington, DC 20003. The Contractor shall supply the agenda for the Kick-Off meeting to the VA COR and Contracting Officer (CO). The Contractor shall also provide the VA project team with Kick-Off meeting minutes. The VA-PM, COR, and CO should be on the list of attendees for this meeting.Deliverables: Kick-Off Meeting AgendaKick-Off Meeting MinutesPROJECT MANAGEMENT ACCOUNTABILITY SYSTEM (PMAS) SUPPORT The Contractor shall support the VA Project Manager (PM) in preparing the required PMAS artifacts in accordance with the OIT ProPath Process Maps as identified in the OIT ProPath Website.? The Contractor shall provide PMAS support to the GRC project staff in planning, implementing, overseeing, and reporting on:? A.??PMAS Data Management.? The Contractor shall plan and report on PMAS data requirements and submissions.? This shall include development of a methodology, and applying that methodology to both routine and ad hoc data requests. B.??PMAS Methodology.? The Contractor shall coordinate with the PM to create and document a methodology for meeting PMAS requirements.? This methodology shall address timelines, process, procedures, templates, data element definitions, roles, and responsibilities for PMAS data management. Following VA PM approval of the proposed methodology, the Contractor shall apply the methodology to capture, maintain, track, and report PMAS data.?? C.??Routine PMAS Reporting.? The Contractor shall perform data capture, validation, and analysis on a routine, recurring basis, in accordance with the approved PMAS Data Collection Methodology defined above.? Once data is compiled, validated, and formatted, the Contractor shall log and store the official submission to create an audit trail. D.??Ad Hoc PMAS Reporting.? For ad hoc data requests (i.e., 3-4 data calls per month), the Contractor shall coordinate with the VA PM, and other Contractor and VA teammates to collect, validate, compile, and analyze data.? Once data is compiled, validated, and formatted, the Contractor shall log and store the official submission to create an audit trail.TASK 1: SPECIFIC GRC SOLUTION REQUIREMENTSVA requires the Contractor to deliver an enterprise wide license, specially configured, existing COTS based, GRC Solution in as a turnkey solution, which will not require additional Government Furnished Equipment (GFE), except for the servers and storage that the GRC Solution will operate on. The GRC Solution shall be capable of performing the following:Provide an enterprise IT solution which supports OMB CM governance and CM standards defined by NIST; Provide an enterprise IT solution which architected to be flexible in nature to supports current and proposed CM vision as recommended as a standard by NIST. (Note: Any deviation from NIST guidance shall be submitted for review and approval by VA.);Provide a turnkey enterprise IT solution with a proven track record of supporting deploying to Government entities supporting FISMA and current Cyber Security Standards as an enterprise IT solution within 120 day time period;Deliver a GRC capability that is able to evolve as OMB, FISMA laws and NIST standards change; Provide an enterprise GRC Solution which supports current ISCM and RM Standards and is able to evolve as those standards change;Centralize IT data and Cyber Security Artifacts to support business workflow for items to include but not limited to Risk Assessments, SSPs, POA&Ms and their related artifacts;Standardize communication mechanisms, where ever possible, with SCAP, capable of both ingest and transmitting information as required;Support Enterprise Work Flows as part of RMF activities including the following: Situational and operational Risk posture and ARI, available as a scored and displayed risk rating, and separated by logical groupings by organization;Provide a RSS which will include: Correlated (multidimensional) Risk Scores, use of the National Vulnerability Database (NVDB), CVSS scoring and trending, a capability to include organization specific vulnerability lists, NIST, and other framework models.Provide timely information on organizational risk posture to include near real-time analysis and reporting and mitigation implementation tracking and performance metrics, as part of ARI;Provide a P/RSS with pre-designed and easily modifiable dashboards for use with many customers from executives to operational staff;Cyber Security vulnerabilities mitigation recommendations are incorporated into VA work streams in near-real-time; Support OMB’s CyberScope reporting requirements;Support assessments for NIST SP 800-53 controls, NIST Risk Management Framework (NIST SP 800-37) as defined by OMB Laws, FISMA laws, NIST standards, VA requirements, governance and policy;Support current NIST SCAP standards (e.g. CVSS 2.0, Common Platform Enumeration (CPE), Common Vulnerability Enumeration (CVE), Common Configuration Enumeration (CCE)) for data exchanges, feeds and collaboration between applications or downstream processing; Support assessments of VA IT assets, as defined by VA requirements;Provide a comprehensive and correlated analysis of both the 800-53 and VA IT asset assessments;Provide an ARI platform for Big Data analytics with Hadoop and specialized data mashing analytics similar to what is required for intelligence agencies, but for ARI, Root Cause Analysis, and predictive risk analytics;Provide all plans with a phased approach, taking into account the size and scope of VA’s systems, network, and users; Contractor’s GRC Solution; and overall complexity of VA’s requested GRC Solution. B.Ease of deploymentShall be capable of being deployed in 60-120 day increments with a proven history of 120 day or less deployments with a COTS GRC Solution, with similar requirements with other federal agencies deploying the same GRC Solution for the purposes of ISCM and RM;Shall integrate seamless with Microsoft Active Directory for user management;Shall be able to implement a multi-tier organizational hierarchy with assets assigned at all tiers with one too many relationship for assets to tiers possible.C.Scalability/PerformanceShall have a multi-tier architecture that scales for all scenarios;Shall be able to support up to 5,000 simultaneous users running reports and assessments (50,000+) along with automated processes running full-lifecycle, ISOs, SOs, Management, etc.;Shall have a proven track record of large-scale data integrationsShall have successful deployments and references for installations in excess of 100,000 users and 100,000 assets;Shall be able support up to 800,000 IP assets and millions of objects (e.g. assets, software, controls, users, etc.).D.Risk Model and Continuous MonitoringShall contain a pre-built risk model that supports the NIST 800-39/800-53 rev 3 approach for risk assessment to include current, future and historical risk assessment in a single integrated solution; Shall be able to be easily updated using vendor provided, timely updates as the Risk Model standards evolve (e.g. NIST SP800-53 rev 4, COBIT 5.0, etc); Shall support CVSS version 2 (NIST/) risk scoring; Shall enable ISCM in an integrated fashion within the single platform adhering to NIST SP800-137.F.Ease of Operation, Use and Sustainability Shall be able to be supported by VA staff and not require resident vendor developers or administrators beyond initial implementation; Shall enable users to build new reports, create new workflows, make User Interface changes, and data model changes without requiring design impact reviews, writing any code, or performing unit and/or system regression testing;Shall be developed on an industry standard platform (e.g. .Net, Java);Shall have an independent business logic layer so that new criteria (e.g. controls, risks, policy) can be added to active processes or workflows without requiring recoding and testing;Shall have clearly defined workflows to enable all A&A, ISCM and RM processes to support enterprise workflow requirements;Shall have a single integrated data model for all of the solution components and core functionality (Data is entered/fed into/stored the system once for all functions/monitoring/compliance reporting);Shall support the aggregation of multiple data types (asset, vulnerability, configuration, ticket, incident, risk, control, policy, etc.) into the data model with error and exception handling, order of precedence, data attribute preference, and filtering along with integration protocol support from Java Database Connectivity/ Open Database Connectivity (JDBC/ODBC), Web Services and file integration. The solution shall provide a data-driven approach that goes beyond providing just initial field mapping and does not require integration engine functions to be coded per integration along with defining the storage of data for specific modules. It shall not require custom code to be written and tested;Shall have pre-built reporting for Federal (e.g. NIST, Defense Information Systems Agency (DISA), etc.), Financial (e.g. Payment Card Industry/ Data Security Standard (PCI/DSS)), and Health related (e.g. HIPAA) compliance including charts, dashboards and summary reports and all C&A/A&A Artifacts and CM dashboards;Shall have a fully documented and exposed object model for many to many relationship supports mainly through the user interface for navigation, search, and reporting;Shall be easy to upgrade and not require vendor on-site support;Shall not have any known, unmitigated or unpatched, documented bugs in excess of six (6) months. J.FunctionalityShall easily allow for exceptions based on waivers and POA&M tracking (small number of steps);Shall provide waiver tracking within the system to include all relevant documentation.TASK TWO: SPECIFIC GRC SOLUTION REQUIREMENTS FOR VA INTEGRATIONThe Contractor shall analyze the VA operational environment and provide a turn-key GRC Solution that will meet the requirements identified in section 5.4. The Contractor shall deliver a GRC Solution that is capable of integrating into VA’s operational environment, which consists of over 600 systems, over 1,500 facilities, over 350,000 workstations, approximately 1,000,000 IT assets, and 5,000 concurrent users and automated processes. The integration requirements that the GRC Solution shall meet are as follows:A Platform independent and deployable product, via web interface to users from IT technical staff to senior VA leadership.Ability to be operating system agnostic, heterogeneous product spanning across a geographically dispersed enterprise network.An architecture that supports the management of at least one million assets noted above including (network devices, software applications, security controls and end-user systems)Capability of accepting and incorporating via standard protocols and data from various data feeds that support IT asset, situational awareness, vulnerability identification, penetration scanning, policy enforcement, and any other data feed (which VA has currently has in inventory or will add in the future, which fills an information security objective including the following known systems:Microsoft System Center Configuration Manager (SCCM)IBM - Tivoli Endpoint Manager (BigFix)Tivoli Endpoint Manager for Lifecycle ManagementTivoli Endpoint Manager for Security and ComplianceTivoli Endpoint Manager for Power ManagementTivoli Endpoint Manager for Patch ManagementGeoVA (ArcGIS)McAfee - Host Based Security System (HBSS)ePolicy Orchestrator (ePO)Agent (Firewall)Asset Baseline MonitorPolicy AuditorHost Intrusion Prevention System (HIPS)Rogue System DetectionVirus Scan Enterprise (AV) Endpoint Data Loss Prevention (DLP)AntiSpywareSiteAdvisorTenable – Nessus Scanner and Security CenterCore Security Technologies – Core ImpactIBM Rational - AppScanHewlett Packard (HP) – WebInspectHP - OpenViewNTO SpiderTrustwave (Intellitactics)Q1Labs QRadarSenSageSplunkCA User Activity Reporting ModuleHP Fortify 360SolarWinds Orion Network Performance Monitor (NPM)CiscoCiscoWorks LAN Management SolutionCisco Network Collector (CNC)RemedyCA UnicenterDBProtect, AppDetective,Also see tools listed in the VA’s ISCM CONOPSScalable and deployable to meet VA’s specific needs as outlined in this PWS and referenced documents.Configurable to integrate into VA’s operational environment and be able to support multi-site deployment with hierarchy and high availability/DR capabilitiesContains the NIST Risk Scoring model and at least two other major risk scoring standards (e.g., COBIT 5, Risk IT Framework, etc.).Should be built around the Continuous Asset Evaluation, Situational Awareness and Risk Scoring (CAESARS) (NIST IR7756, Second Draft) framework extension and NIST ISCM as defined by NIST SP 800-137, which shall serve as the design reference and guidance for VA’s ISCM and RMF program. The GRC Solution should be able to function as the primary component for VA’s ISCM program.Shall be IAW NIST ISCM standards, DHS CAESERS Reference Architecture, and as provided for in this PWS provide an A/RSS, SSS, P/RSS, DBSS, and ISS. The Contractor shall deliver an A/RSS and P/RSS CONOPS.VA user access shall be controlled via the use of secure authentication through VA's Active Directory (AD) by signing onto the VA’s network at a VA site or remotely and then into the GRC Solution.Utilize Single Sign-On (SSO) and be completely integrated with Microsoft AD for access control and authentication.Provides privileged access, enabling restricted views of reports, dashboards and data as required to support sensitive data requirements defined by VA governance (e.g. VA Handbooks), VA management structure and required job roles. Provide timely information on organizational risk posture to include near real-time analysis and reporting and mitigation implementation, mitigation tracking and performance metrics.Provide risk analysis and subsequent risk score (i.e. CVSS and other) of privacy and security events to include the correlated intersects between an actual event, vulnerability, risk, assessment, VA policies, waivers and other related factors.The Contractor shall deliver a Connector Development Plan (IAW industry standard and address the information contained in the ISCM CONOP) which will describe how the GRC Solution will interface with the data sources identified in section 5.4.1 (3) above. Deliverables:Connector Development PlanAnalysis Risk Scoring Subsystem (A/RSS) CONOPSPresentation / Reporting Subsystem (P/RSS) CONOPSTASK THREE – IMPLEMENTATION SUPPORT SERVICESThe Contractor shall provide data, based on previous large scale deployment experience with similar types of systems as described in 5.4.1 (Task Two: Specific GRC Solution Requirements for VA Integration), what the expected network impact should be for their proposed solution on how their network performance ensured the Contractor’s GRC Solution shall function within VA’s operating environment without negative performance to the GRC Solution and VA network. The Contractor shall provide the following GRC Solution implementation support services: Provide a complete list of hardware requirements to VA. Requirements listing will be broken out in phases, which will include a listing of the: (1) minimum requirements, (2) optimum configuration requirements. This shall include, but not limited to, processing needs, storage needs, scalable architecture references, and examples of other system configuration being utilized for large scale deployments. Provide the configuration recommendation taking into account the size and scope of VA’s Enterprise and Contractor’s GRC Solution to include all necessary aspects (e.g. -- all modules, connectors, users, number of assets (as previously referenced), near-real-time analytics, dashboard population, communication to other systems, and all functionality being used in a data warehouse (e.g. Hadoop or equivalent) and very heavy (processor intensive) peak load environment). Meet the following additional capabilities: Put all custom solutions in code escrow available for VA reuse;Ensure all VA data shall be retained and archived in accordance with VA Policy and Federal Government regulations;Insure the proper destruction of all failed or replaced drives, which may contain any VA data, IAW VA policies. This would include, but not be limited to any drive that had or had data that was used to design, build, and or support VA’s implementation of the GRC Solution;Generate a Software SDLC plan for the Contractor’s GRC Solution and all associated components;Plan for the way method updates are provided to VA so VA personnel can insure code and functional integrity before implementation;Provide a Risk and Vulnerability Reduction plan of how known or discovered security vulnerabilities of the GRC Solution and all components are mitigated and later removed.Develop and implement a phased Implementation Plan. This plan shall be developed in accordance with industry standards and be approved by VA. The plan shall include implementation services which would be conducted under the supervision of VA.Implementation phases shall be broken out with clear timeframes, GRC Solution elements (components), functionality of the proposed system, CPMP, Plans, CONOPS, and all other deliverables. The plan shall show how the initial functionality of the GRC Solution will be partially operational by Initial Operational Capabilities (IOC) – as of the time of the release of this PWS, IOC is scheduled for Nov. 15. 2012). At IOC the GRC Solution shall be able to automate FISMA process in order to allow VA to automate a portion of the A&A process for renewing ATOs (in line with OMB regulations and FISMA (2002)).Deliver a Risk Scoring analytics and output display plan for the P/RSS (i.e., graphical dashboard).Deliver a Risk Scoring analytics schema and system for the A/RSS to conduct risk scoring analysis.Deliver a database schema and software system for the DBSS to maintain data output to include analysis and presentation developed by the GRC Solution. Additionally, the DBSS may need to maintain raw data for trending and analysis if the originating database does not and/or cannot store data for the length of time required by VA’s ISCM and RM programs.Deliver an inventory schema and software system for the ISS to maintain Inventory information collected and developed by the GRC Solution.Submit all paperwork necessary and provide technical expertise for the creation of the Assessment and Authorization (A&A) for a system Authority to Operate (ATO).? Deliverables:Software SDLC PlanRisk and Vulnerability Reduction Plan Implementation PlanRisk Scoring Analytics and Output Display PlanA&A Package for proposed GRC SolutionTASK FOUR - SYSTEM DESIGN & ENGINNERING The Contractor shall provide design and engineering analysis that incorporated the GRC Solution into VA’s IT enterprise. Due to the size and scope of this solution, the GRC design and analysis will need to be approved by ISCM RM stakeholders. The design and engineering analysis documented in this section shall support GRC’s requirement to leverage existing capabilities in place in the VA ensuring the success of the overall ISCM RM solution. The design and engineering analysis documentation required are as follows:ISCM RM Gap Analysis (Document current VA capabilities and gaps in support for ISCM RM);Provide ISCM RM CONOPS;Provide ISCM RM Implementation plan and timeline;Hardware / infrastructure Requirements;Provide Prototypes to model IT enterprise data flows and benchmark metrics on data services to support ISCM RM design.Deliverables:ISCM RM Gap Analysis ISCM RM CONOPSISCM RM Implementation plan and timelineHardware / infrastructure Requirements Prototypes to model IT enterprise data flows and benchmark metricsOPTIONAL TASK – HARDWARE/INFRASTRUCTURE EQUIPMENTThe Contractor shall provide Hardware/ Infrastructure equipment necessary to provide a full turn-key solution to VA.Deliverables:GRC Solution Hardware (If Optional Task exercised by VA)TASK FIVE - SYSTEM AVAILABILITYThe Contractor shall be able to meet the required system availability of 99.9% uptime and must be incorporated into a service level agreement (SLA) that provides for and addresses uptime. The Contractor shall manage organizational SLA including, but not limited to developing and monitoring SLA metrics, and establishing escalation procedures. SLAs may include definitions of services, performance measurement, problem management, customer duties, warranties, disaster recovery, and other common elements. The Contractor may assist in the creation of SLAs with both internal and external stakeholders as well as third-party vendors. TASK SIX - MAINTENANCE AND TECHNICAL SUPPORTThe GRC Solution shall be able to be operated by VA with minimal Original Equipment Manufacturer (OEM) staff support for operations, maintenance and support. To ensure VA operates the GRC Solution optimally, the Contractor shall provide maintenance and technical support. The Contractor shall provide technical support, to include help desk support for software on a 24 hours a day, seven days a week, and 365 days a year basis commencing once the systems begins its IOC and during each option year of the contract. Help desk support shall be for VA’s ISCM team administrators, program manager, COR, and the risk analysts for the A/RSS and P/RSS. The Contractor shall respond within a 15 minute window that begins when the Contractor is contacted via phone or email based on an agreed upon reporting plan. The Contractor shall provide the following maintenance documentation:Help Desk Plan and Procedures Guide and means of contact to include phone and web-based support for VA users and system administrators to contact as needed.Contractor Escalation Plan and contact list for outages and similar issues. The Escalation Plan shall detail the processes and procedures in instances where any aspect of the VA Central Office (VACO) Network is not available. The escalation list will include multiple levels of escalation to include executive level contacts at Contractor if VA deems necessary to contact.Contractor developed and/or provided data connectors list to VA systems. The Data Connector List shall describe how each data connector to VA system will be supported.Change Management Plan (CMP) in accordance with industry standards that detail the change management process. The CMP shall include:Change Management process flow requirements; VA’s National Change Control Board (NCCB) procedures as directed by the VA GRC Solution Program Manager and COR; Evaluating and authorizing CSCPs.Address the CMP procedures for software updates and how they will be provided and coordinated with VA and for all necessary and/or requested changes, upgrades and others.Risk scoring and dashboard development and display support for modeling and changes. Document and provide a Risk Scoring and Dashboard Change Procedure.A Troubleshooting Reference Guide that entails the following:Overall process of troubleshooting;Different troubleshooting resources available that details the Help Desk Resources and Executive Contacts;Common questions asked with appropriate actions identified. Deliverables:? Help Desk Plan and Procedures Guide Escalation Plan Data Connectors List Change Management Plan Risk Scoring And Dashboard Change ProceduresTroubleshooting Reference GuideTASK SEVEN - TRAINING The Contractor shall propose a set of training options that fits their GRC Solution that meets, at a minimum, the following types of training: (1) Administrator, (2) Risk Analyst, (3) Presentation (Dashboard) reporting, (4) A&A training, and (5) Inventory database development and management. Items 1-6 are mandatory requirements.On-site GRC Solution system administrator training for up to 10 administrators. Training to be held in Austin, TX and Washington, DC.Training for up to 10 risk analysts during the Base Period. Training to be held in Washington, DC.Training for up to 10 analysts for Presentation (Dashboard) development. Training to be held in Washington, DC.Training for up to 1,500 VA personnel for A&A input and process procedures during the Base Period. Training to be held in four regional locations: TBDTraining for up to 150 administrators and analysts for inventory (e.g - POA&Ms, RAs, SSP) input and process procedures during the Base Period. Training to be held in Washington, DC and Roanoke, VA.Training materials shall be provided for all training provided.The Contractor shall provide materials to be covered in each session to all students – this may be accomplished via hardcopy, Compact Disc (CD), or Web Link within five business days of the end of each training session. The Contractor shall arrange the training schedule through the VA PM/VA COR with 20 business days advance notice. This includes identifying the training requirements in advance.Deliverables:End User Training MaterialsAdministrator Training MaterialsRisk Analyst Training MaterialsOPTIONAL PERIOD 1: The Contractor shall provide the following services:1.The Contractor shall provide software maintenance for all associated elements of the GRC Solution provided during this period. 2.The Contractor shall provide software maintenance (e.g. – license renewal) enterprise licenses for deployed GRC Solution, on a per year basis.3. The Contractor shall provide training options that fits its GRC Solution that meets, at a minimum, the following types of training: (1) Administrator, (2) Risk Analyst, (3) Presentation (Dashboard) reporting, (4) A&A training, and (5) Inventory database development and management. Items 1-3 are mandatory and items 4 and 5 are desirable. Training, priced in increments of 1 day blocks.On-site GRC Solution system administrator training for up to 10 administrators. Training to be held in Austin, TX and Washington, DC.Training for up to five risk analyst during this option year period. Training to be held in Washington, DC.Training for up to five analysts for Presentation (Dashboard) development. Training to be held in Washington, DC.Training for up to 100 VA personnel for A&A input and process procedures during this option year period, to be held in four regional locations: TBD.Training for up to 10 for inventory (e.g - POA&Ms, RAs, SSP) input and process procedures during this option year period. Training to be held in Washington, DC and Roanoke, VA.Training materials will be provided for all training provided.4.The Contractor shall provide 24x7x365 help desk support as defined in section 5.4.5, for a period of 12- months.Deliverables:GRC Enterprise License RenewalUpdates to Training materials (per section 5.4.6)Updates to Help Desk Plan and Procedures Guide 5.4.7.1 Optional Task 1 -- Continuation integration services as described in Section 5.4.1 The contractor shall provide continuation integration services as described in Section 5.4.1 for modules, connectors and potential integration of other VA systems, and third party applications. Deliverables:Updates to Connector Development PlanUpdates to A/RSS CONOPSUpdates to P/RSS CONOPS5.4.7.2 Optional Task 2 -- Dashboard Modification Services The contractor shall provide dashboard modification services to modify the presentation layer of the dashboard integrate into mobile devices; integrate into other VA dashboards, intranet sites, and others as may be required by VA. 5.4.7.3 Optional Task 3 -- Risk Scoring Change Services The contractor shall provide risk scoring change services to modify the risk scoring models, mathematical models, additional correlation of variables, risk variables, algorithm to provide a more intelligent and multidimensional risk scoring model as may be required by VA. OPTIONAL PERIOD 2: The Contractor shall provide the following services:1.The Contractor shall provide software maintenance for all associated elements of the GRC Solution provided during this period. 2.The Contractor shall provide software maintenance (e.g. – license renewal) enterprise licenses for deployed GRC Solution, on a per year basis.3. The Contractor shall provide training options that fits its GRC Solution that meets, at a minimum, the following types of training: (1) Administrator, (2) Risk Analyst, (3) Presentation (Dashboard) reporting, (4) A&A training, and (5) Inventory database development and management. Items 1-3 are mandatory and items 4 and 5 are desirable. Training, priced in increments of 1 day blocks.On-site GRC Solution system administrator training for up to 10 administrators. Training to be held in Austin, TX and Washington, DC.Training for up to five risk analyst during this option year period. Training to be held in Washington, DC.Training for up to five analysts for Presentation (Dashboard) development. Training to be held in Washington, DC.Training for up to 100 VA personnel for A&A input and process procedures during this option year period, to be held in four regional locations: TBD.Training for up to 10 for inventory (e.g - POA&Ms, RAs, SSP) input and process procedures during this option year period. Training to be held in Washington, DC and Roanoke, VA.Training materials will be provided for all training provided.4.The Contractor shall provide 24x7x365 help desk support as defined in section 5.4.5, for a period of 12- months.Deliverables:GRC Enterprise License RenewalUpdates to Training materials (per section 5.4.6)Updates to Help Desk Plan and Procedures Guide 5.4.8.1 Optional Task 1 -- Continuation integration services as described in Section 5.4.1 The contractor shall provide continuation integration services as described in Section 5.4.1 for modules, connectors and potential integration of other VA systems, and third party applications. Deliverables:Updates to Connector Development PlanUpdates to A/RSS CONOPSUpdates to P/RSS CONOPS5.4.8.2 Optional Task 2 -- Dashboard Modification Services The contractor shall provide dashboard modification services to modify the presentation layer of the dashboard integrate into mobile devices; integrate into other VA dashboards, intranet sites, and others as may be required by VA. 5.4.8.3 Optional Task 3 -- Risk Scoring Change Services The contractor shall provide risk scoring change services to modify the risk scoring models, mathematical models, additional correlation of variables, risk variables, algorithm to provide a more intelligent and multidimensional risk scoring model as may be required by VA. 5.4.8.4 Option Task 4 – Engineering / Architecture Modifications (System, Software and Processes) The contractor shall provide changes to the system enabling the system to continue to meet VA’s goals and objectives and accommodate changes in laws, guidance, standards and requirements. The deliverables will be accepted in MS Word and PowerPoint format.Deliverables:Documentation of configuration and architecture changes. OPTIONAL PERIOD 3: The Contractor shall provide the following services:1.The Contractor shall provide software maintenance for all associated elements of the GRC Solution provided during this period. 2.The Contractor shall provide software maintenance (e.g. – license renewal) enterprise licenses for deployed GRC Solution, on a per year basis.3. The Contractor shall provide training options that fits its GRC Solution that meets, at a minimum, the following types of training: (1) Administrator, (2) Risk Analyst, (3) Presentation (Dashboard) reporting, (4) A&A training, and (5) Inventory database development and management. Items 1-3 are mandatory and items 4 and 5 are desirable. Training, priced in increments of 1 day blocks.On-site GRC Solution system administrator training for up to 10 administrators. Training to be held in Austin, TX and Washington, DC.Training for up to five risk analyst during this option year period. Training to be held in Washington, DC.Training for up to five analysts for Presentation (Dashboard) development. Training to be held in Washington, DC.Training for up to 100 VA personnel for A&A input and process procedures during this option year period, to be held in four regional locations: TBD.Training for up to 10 for inventory (e.g - POA&Ms, RAs, SSP) input and process procedures during this option year period. Training to be held in Washington, DC and Roanoke, VA.Training materials will be provided for all training provided.4.The Contractor shall provide 24x7x365 help desk support as defined in section 5.4.5, for a period of 12- months.Deliverables:GRC Enterprise License RenewalUpdates to Training materials (per section 5.4.6)Updates to Help Desk Plan and Procedures Guide 5.4.9.1 Optional Task 1 -- Continuation integration services as described in Section 5.4.1 The contractor shall provide continuation integration services as described in Section 5.4.1 for modules, connectors and potential integration of other VA systems, and third party applications. Deliverables:Updates to Connector Development PlanUpdates to A/RSS CONOPSUpdates to P/RSS CONOPS5.4.9.2 Optional Task 2 -- Dashboard Modification Services The contractor shall provide dashboard modification services to modify the presentation layer of the dashboard integrate into mobile devices; integrate into other VA dashboards, intranet sites, and others as may be required by VA. 5.4.9.3 Optional Task 3 -- Risk Scoring Change Services The contractor shall provide risk scoring change services to modify the risk scoring models, mathematical models, additional correlation of variables, risk variables, algorithm to provide a more intelligent and multidimensional risk scoring model as may be required by VA. 5.4.9.4 Option Task 4 – Engineering / Architecture Modifications (System, Software and Processes) The contractor shall provide changes to the system enabling the system to continue to meet VA’s goals and objectives and accommodate changes in laws, guidance, standards and requirements. The deliverables will be accepted in MS Word and PowerPoint format.Deliverables:Documentation of configuration and architecture changes. OPTIONAL PERIOD 4: The Contractor shall provide the following services:1.The Contractor shall provide software maintenance for all associated elements of the GRC Solution provided during this period. 2.The Contractor shall provide software maintenance (e.g. – license renewal) enterprise licenses for deployed GRC Solution, on a per year basis.3. The Contractor shall provide training options that fits its GRC Solution that meets, at a minimum, the following types of training: (1) Administrator, (2) Risk Analyst, (3) Presentation (Dashboard) reporting, (4) A&A training, and (5) Inventory database development and management. Items 1-3 are mandatory and items 4 and 5 are desirable. Training, priced in increments of 1 day blocks.On-site GRC Solution system administrator training for up to 10 administrators. Training to be held in Austin, TX and Washington, DC.Training for up to five risk analyst during this option year period. Training to be held in Washington, DC.Training for up to five analysts for Presentation (Dashboard) development. Training to be held in Washington, DC.Training for up to 100 VA personnel for A&A input and process procedures during this option year period, to be held in four regional locations: TBD.Training for up to 10 for inventory (e.g - POA&Ms, RAs, SSP) input and process procedures during this option year period. Training to be held in Washington, DC and Roanoke, VA.Training materials will be provided for all training provided.4.The Contractor shall provide 24x7x365 help desk support as defined in section 5.4.5, for a period of 12- months.Deliverables:GRC Enterprise License RenewalUpdates to Training materials (per section 5.4.6)Updates to Help Desk Plan and Procedures Guide 5.4.10.1 Optional Task 1 -- Continuation integration services as described in Section 5.4.1 The contractor shall provide continuation integration services as described in Section 5.4.1 for modules, connectors and potential integration of other VA systems, and third party applications. Deliverables:Updates to Connector Development PlanUpdates to A/RSS CONOPSUpdates to P/RSS CONOPS5.4.10.2 Optional Task 2 -- Dashboard Modification Services The contractor shall provide dashboard modification services to modify the presentation layer of the dashboard integrate into mobile devices; integrate into other VA dashboards, intranet sites, and others as may be required by VA. 5.4.10.3 Optional Task 3 -- Risk Scoring Change Services The contractor shall provide risk scoring change services to modify the risk scoring models, mathematical models, additional correlation of variables, risk variables, algorithm to provide a more intelligent and multidimensional risk scoring model as may be required by VA. 5.4.10.4 Option Task 4 – Engineering / Architecture Modifications (System, Software and Processes) The contractor shall provide changes to the system enabling the system to continue to meet VA’s goals and objectives and accommodate changes in laws, guidance, standards and requirements. The deliverables will be accepted in MS Word and PowerPoint format.Deliverables:Documentation of configuration and architecture changes. GENERAL REQUIREMENTSThe Contractor shall be required to follow the Veterans Affairs Office of Information Technology’s (OIT) policies and procedures, set forth in "VA Information and Information System Security/Privacy Requirements for IT Contracts” located at the following Web site: .” ENTERPRISE AND IT FRAMEWORKThe Contractor shall support the VA enterprise management framework. In association with the framework, the Contractor shall comply with OIT Technical Reference Model (One-VA TRM). One-VA TRM is one component within the overall Enterprise Architecture (EA) that establishes a common vocabulary and structure for describing the information technology used to develop, operate, and maintain enterprise applications. One-VA TRM includes the Standards Profile and Product List that collectively serves as a VA technology roadmap. Architecture, Strategy, and Design (ASD) has overall responsibility for the One-VA TRM.The Contractor solution shall support the latest Internet Protocol Version 6 (IPv6) based upon the directive issued by the Office of Management and Budget (OMB) on September 28, 2010 (). IPv6 technology, in accordance with the USGv6 Profile (NIST Special Publication (SP) 500-267, ) and NIST SP 800 series applicable compliance, shall be included in all IT infrastructures, application designs, application development, operational systems and sub-systems, and their integration. All public/external facing servers and services (e.g. web, email, DNS, ISP services, etc) shall support native IPv6 users and all internal infrastructure and applications shall operate using native IPv6. To ensure interoperability, IPv4 will coexist during the transition to IPv6 and it is expected that VA will continue running IPv4 until it is phased out by 2015. By 2015, all computing, application, and network resources must turn off IPv4 as a communication mechanism in VA, unless a waiver is obtained from the Office of the Principal Deputy Assistant Secretary for Information and Technology, Department of Veterans Affairs or the device/service runs in an enclave. The Contractor IT end user solution that is developed for use on standard VA computers shall be compatible with and be supported on the standard VA operating system, currently Windows 7 (64bit), Internet Explorer 9 and Microsoft Office 2010. However, the migration from Windows XP to Windows 7 is not yet complete within all of VA. As a result, compatibility with and support on Windows XP, Internet Explorer 7 and Microsoft Office 2007 are also required until April 2014 when Microsoft’s extended support for Windows XP ends. In addition, the Contractor IT solution shall be deployable using System Center Configuration Manager (SCCM) tool.The Contractor shall support VA efforts in accordance with the Project Management Accountability System (PMAS) that mandates all new VA IT projects/programs use an incremental development approach, requiring frequent delivery milestones that deliver new capabilities for business sponsors to test and accept functionality. Implemented by the Assistant Secretary for IT, PMAS is a VA-wide initiative to better empower the OIT Project Managers and teams to meet their mission: delivering world-class IT products that meet business needs on time and within budget. The Contractor shall utilize ProPath, the OIT-wide process management tool that assists in the execution of an IT project (including adherence to PMAS standards). It is a one-stop shop providing critical links to the formal approved processes, artifacts, and templates to assist project teams in facilitating their PMAS-compliant work. ProPath is used to build schedules to meet project requirements, regardless of the development methodology employed. POSITION/TASK RISK DESIGNATION LEVEL(S) AND CONTRACTOR PERSONNEL SECURITY REQUIREMENTSPosition SensitivityBackground Investigation (in accordance with Department of Veterans Affairs 0710 Handbook, “Personnel Security Suitability Program,” Appendix A)LowNational Agency Check with Written Inquiries (NACI) A NACI is conducted by OPM and covers a 5-year period. It consists of a review of records contained in the OPM Security Investigations Index (SII) and the DOD Defense Central Investigations Index (DCII), FBI name check, FBI fingerprint check, and written inquiries to previous employers and references listed on the application for employment. In VA it is used for Non-sensitive or Low Risk positions.ModerateModerate Background Investigation (MBI) A MBI is conducted by OPM and covers a 5-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check], a credit report covering a period of 5 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, law enforcement check; and a verification of the educational degree.High Background Investigation (BI) A BI is conducted by OPM and covers a 10-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check report], a credit report covering a period of 10 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, spouse, neighbors, supervisor, co-workers; court records, law enforcement check, and a verification of the educational degree.The Tasks identified below and the resulting Position Sensitivity and Background Investigation delineate the Background Investigation requirements by Contractor individual, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each individual, based upon the tasks the Contractor individual will be working, based upon their submitted proposal.LOW RISK DESIGNATION TASKSPosition Sensitivity and Background Investigation - The position sensitivity and the level of background investigation commensurate with the required level of access for task(s) 5.1.1; 5.1.2; 5.2; and 5.3 within the Performance Work Statement is: FORMCHECKBOX Low/NACIMODERATE RISK DESIGNATION TASKSPosition Sensitivity and Background Investigation - The position sensitivity and the level of background investigation commensurate with the required level of access for task(s) 5.4 (Task 1); 5.4.1 (Task 2); 5.4.2 (Task 3); 5.4.4 (Task 5); 5.4.5 (Task 6); and 5.4.6 (Task 7) within the Performance Work Statement is: FORMCHECKBOX Moderate/MBIHIGH RISK DESIGNATION TASKSPosition Sensitivity and Background Investigation - The position sensitivity and the level of background investigation commensurate with the required level of access for task(s) 5.4.3 (Task 4) within the Performance Work Statement is: FORMCHECKBOX High/BI CONTRACTOR PERSONNEL SECURITY REQUIREMENTSContractor Responsibilities: The Contractor shall prescreen all personnel requiring access to the computer systems to ensure they maintain the appropriate Background Investigation, and are able to read, write, speak and understand the English language.The Contractor shall bear the expense of obtaining background investigations. Within 3 business days after award, the Contractor shall provide a roster of Contractor and Subcontractor employees to the COR to begin their background investigations. The roster shall contain the Contractor’s Full Name, Full Social Security Number, Date of Birth, Place of Birth, and individual background investigation level requirement (based upon Section 6.2 Tasks).The Contractor should coordinate the location of the nearest VA fingerprinting office through the COR. Only electronic fingerprints are authorized.For a Low Risk designation the following forms are required to be completed: 1.OF-306 and 2. DVA Memorandum – Electronic Fingerprints. For Moderate or High Risk the following forms are required to be completed: 1. VA Form 0710 and 2. DVA Memorandum – Electronic Fingerprints. These should be submitted to the COR within 5 business days after award. The Contractor personnel will receive an email notification from the Security and Investigation Center (SIC), through the Electronics Questionnaire for Investigations Processes (e-QIP) identifying the website link that includes detailed instructions regarding completion of the investigation documents (SF85, SF85P, or SF 86). The Contractor personnel shall submit all required information related to their background investigations utilizing the Office of Personnel Management’s (OPM) Electronic Questionnaire for Investigations Processing (e-QIP).The Contractor is to certify and release the e-QIP document, print and sign the signature pages, and send them to the COR for electronic submission to the SIC. These should be submitted to the COR within 3 business days of receipt of the e-QIP notification email.The Contractor shall be responsible for the actions of all personnel provided to work for VA under this contract. In the event that damages arise from work performed by Contractor provided personnel, under the auspices of this contract, the Contractor shall be responsible for all resources necessary to remedy the incident.A Contractor may be granted unescorted access to VA facilities and/or access to VA Information Technology resources (network and/or protected data) with a favorably adjudicated Special Agreement Check (SAC) or “Closed, No Issues” (SAC) finger print results, training delineated in VA Handbook 6500.6 (Appendix C, Section 9), and, the signed “Contractor Rules of Behavior.” However, the Contractor will be responsible for the actions of the Contractor personnel they provide to perform work for VA. The investigative history for Contractor personnel working under this contract must be maintained in the database of the Office of Personnel Management (OPM). The Contractor, when notified of an unfavorably adjudicated background investigation on a Contractor employee as determined by the Government, shall withdraw the employee from consideration in working under the contract.Failure to comply with the Contractor personnel security investigative requirements may result in termination of the contract for default.METHOD AND DISTRIBUTION OF DELIVERABLESThe Contractor shall deliver documentation in electronic format, unless otherwise directed in Section B of the solicitation/contract. Acceptable electronic media include: MS Word 2000/2003/2007/2010, MS Excel 2000/2003/2007/2010, MS PowerPoint 2000/2003/2007/2010, MS Project 2000/2003/2007/2010, MS Access 2000/2003/2007/2010, MS Visio 2000/2002/2003/2007/2010, AutoCAD 2002/2004/2007/2010, and Adobe Postscript Data Format (PDF). PERFORMANCE METRICSThe table below defines the Performance Standards and Acceptable Performance Levels for Objectives associated with this effort. Performance ObjectivePerformance StandardAcceptable Performance LevelsTechnical NeedsShows understanding of requirementsEfficient and effective in meeting requirements Meets technical needs and mission requirementsOffers quality services/productsSatisfactory or higherProject Milestones and ScheduleQuick response capabilityProducts completed, reviewed, delivered in timely mannerNotifies customer in advance of potential problemsSatisfactory or higher3. Project StaffingCurrency of expertisePersonnel possess necessary knowledge, skills and abilities to perform tasksSatisfactory or higher4. Value AddedProvided valuable service to GovernmentServices/products delivered were of desired qualitySatisfactory or higherPerformance ObjectivePerformance StandardAcceptable Performance LevelsEffective CommunicationNo less than 3 contacts per week from Contractor during Base Year100% of the timeGRC Solution AvailabilityMaintain GRC Solution Availability 24/7__99.9___% or better availability, measured on a monthly basisResponse to VA QueryResponses received within 4 business hours of request95% of the time measured on a monthly basisRequired ReportsSubmit required reports on a weekly, monthly, or yearly as called for99% of the time measured on a monthly basisTraining Materials Provide Training materials within 10 days of contract start100% of the time The Government will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the Contractor is performing the services required by this PWS in an acceptable manner. The Government reserves the right to alter or change the surveillance methods in the QASP at its own discretion. A Performance Based Service Assessment Survey will be used in combination with the QASP to assist the Government in determining acceptable performance levels. FACILITY/RESOURCE PROVISIONS The PWS requires the tasks identified to be performed at the Contractor’s facilities. However, in the event if the task to be perform requires extended stay at a Government facility (ie, implementation task), the Government may elect to provide office space, telephone service and system access when authorized contract staff work at a Government location as required in order to accomplish the Tasks associated with this PWS. All procedural guides, reference materials, and program documentation for the project and other Government applications will also be provided on an as-needed basis.The Contractor shall request other Government documentation deemed pertinent to the work accomplishment directly from the Government officials with whom the Contractor has contact. The Contractor shall consider the COR as the final source for needed Government documentation when the Contractor fails to secure the documents by other means. The Contractor is expected to use common knowledge and resourcefulness in securing all other reference materials, standard industry publications, and related materials that are pertinent to the work.VA will provide access to VA specific systems/network as required for execution of the task via remote access technology (e.g. Citrix Access Gateway (CAG), site-to-site VPN, or VA Remote Access Security Compliance Update Environment (RESCUE)). This remote access will provide access to VA specific software such as Veterans Health Information System and Technology Architecture (VistA), ClearQuest, ProPath, Primavera, and Remedy, including appropriate seat management and user licenses. The Contractor shall utilize Government-provided software development and test accounts, document and requirements repositories, etc. as required for the development, storage, maintenance and delivery of products within the scope of this effort.?The Contractor shall not transmit, store or otherwise maintain sensitive data or products in Contractor systems (or media) within the VA firewall IAW VA Handbook 6500.6 dated March 12, 2010. All VA sensitive information shall be protected at all times in accordance with local security field office System Security Plans (SSP’s) and Authority to Operate (ATO)’s for all systems/LAN’s accessed while performing the tasks detailed in this PWS. For detailed Security and Privacy Requirements refer to ADDENDUM A and ADDENDUM B. GOVERNMENT FURNISHED PROPERTYThe Contractor will be provided six laptops for communicating and maintain secure communications with VA. The equipment list will be maintained by the assigned GCS Solution’s COR. ADDENDUM A (Cyber and Information Security Requirements)Cyber and Information Security Requirements for VA IT ServicesThe Contractor shall ensure adequate LAN/Internet, data, information, and system security in accordance with VA standard operating procedures and standard PWS language, conditions, laws, and regulations.?The Contractor’s firewall and web server shall meet or exceed VA minimum requirements for security.?All VA data shall be protected behind an approved firewall.?Any security violations or attempted violations shall be reported to the VA Program Manager and VA Information Security Officer as soon as possible.?The Contractor shall follow all applicable VA policies and procedures governing information security, especially those that pertain to certification and accreditation.Contractor supplied equipment, PCs of all types, equipment with hard drives, etc. for contract services must meet all security requirements that apply to Government Furnished Equipment (GFE) and Government Owned Equipment (GOE).?Security Requirements include:?a) VA Approved Encryption Software must be installed on all laptops or mobile devices before placed into operation, b) Bluetooth equipped devices are prohibited within VA; Bluetooth must be permanently disabled or removed from the device, c) VA approved anti-virus and firewall software, d) Equipment must meet all VA sanitization requirements and procedures before disposal.? The COR, CO, the Project Manager, and the Information Security Officer (ISO) must be notified and verify all security requirements have been adhered to.Each documented initiative under this contract incorporates the VA Handbook 6500.6, “Contract Security,” March 12, 2010 by reference as though fully set forth therein. The VA Handbook 6500.6, “Contract Security” shall also be included in every related agreement, contract or order.?The VA Handbook 6500.6, Appendix C, is included in this document as Addendum B.Training requirements: The Contractor shall complete all mandatory training courses on the current VA training site, the VA Talent Management System (TMS), and will be tracked therein. The TMS may be accessed at . If you do not have a TMS profile, go to and click on the “Create New User” link on the TMS to gain access.Contractor employees shall complete a VA Systems Access Agreement if they are provided access privileges as an authorized user of the computer system of VA.VA Enterprise Architecture ComplianceThe applications, supplies, and services furnished under this contract must comply with One-VA Enterprise Architecture (EA), available at in force at the time of issuance of this contract, including the Program Management Plan and VA's rules, standards, and guidelines in the Technical Reference Model/Standards Profile (TRMSP).? The VA reserves the right to assess contract deliverables for EA compliance prior to acceptance. VA Internet and Intranet Standards:The Contractor shall adhere to and comply with VA Directive 6102 and VA Handbook 6102, Internet/Intranet Services, including applicable amendments and changes, if the Contractor’s work includes managing, maintaining, establishing and presenting information on VA’s Internet/Intranet Service Sites.?This pertains, but is not limited to: creating announcements; collecting information; databases to be accessed, graphics and links to external sites. Internet/Intranet Services Directive 6102 is posted at (copy and paste the following URL to browser): Services Handbook 6102 is posted at (copy and paste following URL to browser): of the Federal Accessibility Law Affecting All Electronic and Information Technology Procurements? (Section 508)On August 7, 1998, Section 508 of the Rehabilitation Act of 1973 was amended to require that when Federal departments or agencies develop, procure, maintain, or use Electronic and Information Technology, that they shall ensure it allows Federal employees with disabilities to have access to and use of information and data that is comparable to the access to and use of information and data by other Federal employees.? Section 508 required the Architectural and Transportation Barriers Compliance Board (Access Board) to publish standards setting forth a definition of electronic and information technology and the technical and functional criteria for such technology to comply with Section 508. These standards have been developed are published with an effective date of December 21, 2000. Federal departments and agencies shall develop all Electronic and Information Technology requirements to comply with the standards found in 36 CFR 1194.Section 508 – Electronic and Information Technology (EIT) Standards:The Section 508 standards established by the Architectural and Transportation Barriers Compliance Board (Access Board) are incorporated into, and made part of all VA orders, solicitations and purchase orders developed to procure Electronic and Information Technology (EIT). These standards are found in their entirety at: and . A printed copy of the standards will be supplied upon request.? The Contractor shall comply with the technical standards as marked: _x_§ 1194.21 Software applications and operating systems_x_§ 1194.22 Web-based intranet and internet information and applications_x_§ 1194.23 Telecommunications products_x_§ 1194.24 Video and multimedia products_x_§ 1194.25 Self contained, closed products_x_§ 1194.26 Desktop and portable computers_x_§ 1194.31 Functional Performance Criteria_x_§ 1194.41 Information, Documentation, and SupportThe standards do not require the installation of specific accessibility-related software or the attachment of an assistive technology device, but merely require that the EIT be compatible with such software and devices so that it can be made accessible if so required by the agency in the future.Physical Security & Safety Requirements:The Contractor and their personnel shall follow all VA policies, standard operating procedures, applicable laws and regulations while on VA property.?Violations of VA regulations and policies may result in citation and disciplinary measures for persons violating the law.The Contractor and their personnel shall wear visible identification at all times while they are on the premises.The VA does not provide parking spaces at the work site; the Contractor must obtain parking at the work site if needed.?It is the responsibility of the Contractor to park in the appropriate designated parking areas. The VA will not invalidate or make reimbursement for parking violations of the Contractor under any conditions.Smoking is prohibited inside/outside any building other than the designated smoking areas.Possession of weapons is prohibited.The Contractor shall obtain all necessary licenses and/or permits required to perform the work, with the exception of software licenses that need to be procured from a Contractor or vendor in accordance with the requirements document. The Contractor shall take all reasonable precautions necessary to protect persons and property from injury or damage during the performance of this contract.Confidentiality and Non-DisclosureThe Contractor shall follow all VA rules and regulations regarding information security to prevent disclosure of sensitive information to unauthorized individuals or organizations.The Contractor may have access to Protected Health Information (PHI) and Electronic Protected Health Information (EPHI) that is subject to protection under the regulations issued by the Department of Health and Human Services, as mandated by the Health Insurance Portability and Accountability Act of 1996 (HIPAA); 45 CFR Parts 160 and 164, Subparts A and E, the Standards for Privacy of Individually Identifiable Health Information (“Privacy Rule”); and 45 CFR Parts 160 and 164, Subparts A and C, the Security Standard (“Security Rule”).?Pursuant to the Privacy and Security Rules, the Contractor must agree in writing to certain mandatory provisions regarding the use and disclosure of PHI and EPHI.??The Contractor will have access to some privileged and confidential materials of VA.?These printed and electronic documents are for internal use only, are not to be copied or released without permission, and remain the sole property of VA.?Some of these materials are protected by the Privacy Act of 1974 (revised by PL 93-5791) and Title 38.?Unauthorized disclosure of Privacy Act or Title 38 covered materials is a criminal offense.The VA Contracting Officer will be the sole authorized official to release in writing, any data, draft deliverables, final deliverables, or any other written or printed materials pertaining to this contract. The Contractor shall release no information.?Any request for information relating to this contract presented to the Contractor shall be submitted to the VA Contracting Officer for response.Contractor personnel recognize that in the performance of this effort, Contractor personnel may receive or have access to sensitive information, including information provided on a proprietary basis by carriers, equipment manufacturers and other private or public entities.?Contractor personnel agree to safeguard such information and use the information exclusively in the performance of this contract.?Contractor shall follow all VA rules and regulations regarding information security to prevent disclosure of sensitive information to unauthorized individuals or organizations as enumerated in this section and elsewhere in this Contract and its subparts and appendices.Contractor shall limit access to the minimum number of personnel necessary for contract performance for all information considered sensitive or proprietary in nature.?If the Contractor is uncertain of the sensitivity of any information obtained during the performance this contract, the Contractor has a responsibility to ask the VA Contracting Officer.Contractor shall train all of their employees involved in the performance of this contract on their roles and responsibilities for proper handling and nondisclosure of sensitive VA or proprietary information.?Contractor personnel shall not engage in any other action, venture or employment wherein sensitive information shall be used for the profit of any party other than those furnishing the information. The sensitive information transferred, generated, transmitted, or stored herein is for VA benefit and ownership alone. Contractor shall maintain physical security at all facilities housing the activities performed under this contract, including any Contractor facilities according to VA-approved guidelines and directives.?The Contractor shall ensure that security procedures are defined and enforced to ensure all personnel who are provided access to patient data must comply with published procedures to protect the privacy and confidentiality of such information as required by VA.Contractor must adhere to the following:The use of “thumb drives” or any other medium for transport of information is expressly prohibited.Controlled access to system and security software and documentation.Recording, monitoring, and control of passwords and privileges.All terminated personnel are denied physical and electronic access to all data, program listings, data processing equipment and systems.VA, as well as any Contractor (or Subcontractor) systems used to support development, provide the capability to cancel immediately all access privileges and authorizations upon employee termination.Contractor PM and VA PM are informed within twenty-four (24) hours of any employee termination.Acquisition sensitive information shall be marked "Acquisition Sensitive" and shall be handled as "For Official Use Only (FOUO)".Contractor does not require access to classified data.Regulatory standard of conduct governs all personnel directly and indirectly involved in procurements.?All personnel engaged in procurement and related activities shall conduct business in a manner above reproach and, except as authorized by statute or regulation, with complete impartiality and with preferential treatment for none.? The general rule is to strictly avoid any conflict of interest or even the appearance of a conflict of interest in VA/Contractor relationships.ADDENDUM B (6500.6, APPENDIX C, APPLICABLE PARAGRAPHS)APPLICABLE PARAGRAPHS TAILORED FROM: THE VA INFORMATION AND INFORMATION SYSTEM SECURITY/PRIVACY LANGUAGE, VA HANDBOOK 6500.6, APPENDIX C, MARCH 12, 2010GENERALContractors, Contractor personnel, Subcontractors, and Subcontractor personnel shall be subject to the same Federal laws, regulations, standards, and VA Directives and Handbooks as VA and VA personnel regarding information and information system security.ACCESS TO VA INFORMATION AND VA INFORMATION SYSTEMSA Contractor/Subcontractor shall request logical (technical) or physical access to VA information and VA information systems for their employees, Subcontractors, and affiliates only to the extent necessary to perform the services specified in the contract, agreement, or task order.All Contractors, Subcontractors, and third-party servicers and associates working with VA information are subject to the same investigative requirements as those of VA appointees or employees who have access to the same types of information. The level and process of background security investigations for Contractors must be in accordance with VA Directive and Handbook 0710, Personnel Suitability and Security Program. The Office for Operations, Security, and Preparedness is responsible for these policies and procedures.Contract personnel who require access to national security programs must have a valid security clearance. National Industrial Security Program (NISP) was established by Executive Order 12829 to ensure that cleared U.S. defense industry contract personnel safeguard the classified information in their possession while performing work on contracts, programs, bids, or research and development efforts. The Department of Veterans Affairs does not have a Memorandum of Agreement with Defense Security Service (DSS). Verification of a Security Clearance must be processed through the Special Security Officer located in the Planning and National Security Service within the Office of Operations, Security, and Preparedness.Custom software development and outsourced operations must be located in the U.S. to the maximum extent practical. If such services are proposed to be performed abroad and are not disallowed by other VA policy or mandates, the Contractor/ Subcontractor must state where all non-U.S. services are provided and detail a security plan, deemed to be acceptable by VA, specifically to address mitigation of the resulting problems of communication, control, data protection, and so forth. Location within the U.S. may be an evaluation factor. The Contractor or Subcontractor must notify the Contracting Officer immediately when an employee working on a VA system or with access to VA information is reassigned or leaves the Contractor or Subcontractor’s employ. The Contracting Officer must also be notified immediately by the Contractor or Subcontractor prior to an unfriendly termination.VA INFORMATION CUSTODIAL LANGUAGEInformation made available to the Contractor or Subcontractor by VA for the performance or administration of this contract or information developed by the Contractor/Subcontractor in performance or administration of the contract shall be used only for those purposes and shall not be used in any other way without the prior written agreement of VA. This clause expressly limits the Contractor/Subcontractor's rights to use data as described in Rights in Data - General, FAR 52.227-14(d) (1).VA information should not be co-mingled, if possible, with any other data on the Contractors/Subcontractor’s information systems or media storage systems in order to ensure VA requirements related to data protection and media sanitization can be met. If co-mingling must be allowed to meet the requirements of the business need, the Contractor must ensure that VA’s information is returned to the VA or destroyed in accordance with VA’s sanitization requirements. VA reserves the right to conduct on site inspections of Contractor and Subcontractor IT resources to ensure data security controls, separation of data and job duties, and destruction/media sanitization procedures are in compliance with VA directive requirements.Prior to termination or completion of this contract, Contractor/Subcontractor must not destroy information received from VA, or gathered/created by the Contractor in the course of performing this contract without prior written approval by VA. Any data destruction done on behalf of VA by a Contractor/Subcontractor must be done in accordance with National Archives and Records Administration (NARA) requirements as outlined in VA Directive 6300, Records and Information Management and its Handbook 6300.1 Records Management Procedures, applicable VA Records Control Schedules, and VA Handbook 6500.1, Electronic Media Sanitization. Self-certification by the Contractor that the data destruction requirements above have been met must be sent to the VA Contracting Officer within 30 days of termination of the contract.The Contractor/Subcontractor must receive, gather, store, back up, maintain, use, disclose and dispose of VA information only in compliance with the terms of the contract and applicable Federal and VA information confidentiality and security laws, regulations and policies. If Federal or VA information confidentiality and security laws, regulations and policies become applicable to the VA information or information systems after execution of the contract, or if NIST issues or updates applicable FIPS or Special Publications (SP) after execution of this contract, the parties agree to negotiate in good faith to implement the information confidentiality and security laws, regulations and policies in this contract. The Contractor/Subcontractor shall not make copies of VA information except as authorized and necessary to perform the terms of the agreement or to preserve electronic information stored on Contractor/Subcontractor electronic storage media for restoration in case any electronic equipment or data used by the Contractor/Subcontractor needs to be restored to an operating state. If copies are made for restoration purposes, after the restoration is complete, the copies must be appropriately destroyed. If VA determines that the Contractor has violated any of the information confidentiality, privacy, and security provisions of the contract, it shall be sufficient grounds for VA to withhold payment to the Contractor or third party or terminate the contract for default or terminate for cause under Federal Acquisition Regulation (FAR) part 12. If a VHA contract is terminated for cause, the associated Business Associate Agreement (BAA) must also be terminated and appropriate actions taken in accordance with VHA Handbook 1600.01, Business Associate Agreements. Absent an agreement to use or disclose protected health information, there is no business associate relationship. The Contractor/Subcontractor must store, transport, or transmit VA sensitive information in an encrypted form, using VA-approved encryption tools that are, at a minimum, FIPS 140-2 validated.The Contractor/Subcontractor’s firewall and Web services security controls, if applicable, shall meet or exceed VA’s minimum requirements. VA Configuration Guidelines are available upon request.Except for uses and disclosures of VA information authorized by this contract for performance of the contract, the Contractor/Subcontractor may use and disclose VA information only in two other situations: (i) in response to a qualifying order of a court of competent jurisdiction, or (ii) with VA’s prior written approval. The Contractor/Subcontractor must refer all requests for, demands for production of, or inquiries about, VA information and information systems to the VA contracting officer for response.Notwithstanding the provision above, the Contractor/Subcontractor shall not release VA records protected by Title 38 U.S.C. 5705, confidentiality of medical quality assurance records and/or Title 38 U.S.C. 7332, confidentiality of certain health records pertaining to drug addiction, sickle cell anemia, alcoholism or alcohol abuse, or infection with human immunodeficiency virus. If the Contractor/Subcontractor is in receipt of a court order or other requests for the above mentioned information, that Contractor/Subcontractor shall immediately refer such court orders or other requests to the VA contracting officer for response.For service that involves the storage, generating, transmitting, or exchanging of VA sensitive information but does not require C&A or a Memorandum of Understanding-Interconnection Service Agreement (MOU-ISA) for system interconnection, the Contractor/Subcontractor must complete a Contractor Security Control Assessment (CSCA) on a yearly basis and provide it to the RMATION SYSTEM DESIGN AND DEVELOPMENTInformation systems that are designed or developed for or on behalf of VA at non-VA facilities shall comply with all VA directives developed in accordance with FISMA, HIPAA, NIST, and related VA security and privacy control requirements for Federal information systems. This includes standards for the protection of electronic PHI, outlined in 45 C.F.R. Part 164, Subpart C, information and system security categorization level designations in accordance with FIPS 199 and FIPS 200 with implementation of all baseline security controls commensurate with the FIPS 199 system security categorization (reference Appendix D of VA Handbook 6500, VA Information Security Program). During the development cycle a Privacy Impact Assessment (PIA) must be completed, provided to the COR, and approved by the VA Privacy Service in accordance with Directive 6508, VA Privacy Impact Assessment.The Contractor/Subcontractor shall certify to the COR that applications are fully functional and operate correctly as intended on systems using the VA Federal Desktop Core Configuration (FDCC), and the common security configuration guidelines provided by NIST or VA. This includes Internet Explorer 7 configured to operate on Windows XP and Vista (in Protected Mode on Vista) and future versions, as required.The standard installation, operation, maintenance, updating, and patching of software shall not alter the configuration settings from the VA approved and FDCC configuration. Information technology staff must also use the Windows Installer Service for installation to the default “program files” directory and silently install and uninstall.Applications designed for normal end users shall run in the standard user context without elevated system administration privileges.The security controls must be designed, developed, approved by VA, and implemented in accordance with the provisions of VA security system development life cycle as outlined in NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems, VA Handbook 6500, Information Security Program and VA Handbook 6500.5, Incorporating Security and Privacy in System Development Lifecycle. The Contractor/Subcontractor is required to design, develop, or operate a System of Records Notice (SOR) on individuals to accomplish an agency function subject to the Privacy Act of 1974, (as amended), Public Law 93-579, December 31, 1974 (5 U.S.C. 552a) and applicable agency regulations. Violation of the Privacy Act may involve the imposition of criminal and civil penalties.The Contractor/Subcontractor agrees to:Comply with the Privacy Act of 1974 (the Act) and the agency rules and regulations issued under the Act in the design, development, or operation of any system of records on individuals to accomplish an agency function when the contract specifically identifies:The Systems of Records (SOR); andThe design, development, or operation work that the Contractor/Subcontractor is to perform;Include the Privacy Act notification contained in this contract in every solicitation and resulting subcontract and in every subcontract awarded without a solicitation, when the work statement in the proposed subcontract requires the redesign, development, or operation of a SOR on individuals that is subject to the Privacy Act; andInclude this Privacy Act clause, including this subparagraph (3), in all subcontracts awarded under this contract which requires the design, development, or operation of such a SOR.In the event of violations of the Act, a civil action may be brought against the agency involved when the violation concerns the design, development, or operation of a SOR on individuals to accomplish an agency function, and criminal penalties may be imposed upon the officers or employees of the agency when the violation concerns the operation of a SOR on individuals to accomplish an agency function. For purposes of the Act, when the contract is for the operation of a SOR on individuals to accomplish an agency function, the Contractor/Subcontractor is considered to be an employee of the agency.“Operation of a System of Records” means performance of any of the activities associated with maintaining the SOR, including the collection, use, maintenance, and dissemination of records.“Record” means any item, collection, or grouping of information about an individual that is maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and contains the person’s name, or identifying number, symbol, or any other identifying particular assigned to the individual, such as a fingerprint or voiceprint, or a photograph.“System of Records” means a group of any records under the control of any agency from which information is retrieved by the name of the individual or by some identifying number, symbol, or other identifying particular assigned to the individual.The vendor shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as “Systems”), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hot fixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems.The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, but in no event longer than 5 days. When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to VA that the patch has been validated as not affecting the Systems within 10 working days.All other vulnerabilities shall be remediated as specified in this paragraph in a timely manner based on risk, but within 60 days of discovery or disclosure. Exceptions to this paragraph (e.g. for the convenience of VA) shall only be granted with approval of the contracting officer and the VA Assistant Secretary for Office of Information and RMATION SYSTEM HOSTING, OPERATION, MAINTENANCE, OR USEFor information systems that are hosted, operated, maintained, or used on behalf of VA at non-VA facilities, Contractors/Subcontractors are fully responsible and accountable for ensuring compliance with all HIPAA, Privacy Act, FISMA, NIST, FIPS, and VA security and privacy directives and handbooks. This includes conducting compliant risk assessments, routine vulnerability scanning, system patching and change management procedures, and the completion of an acceptable contingency plan for each system. The Contractor’s security control procedures must be equivalent, to those procedures used to secure VA systems. A Privacy Impact Assessment (PIA) must also be provided to the COR and approved by VA Privacy Service prior to operational approval. All external Internet connections to VA’s network involving VA information must be reviewed and approved by VA prior to implementation.Adequate security controls for collecting, processing, transmitting, and storing of Personally Identifiable Information (PII), as determined by the VA Privacy Service, must be in place, tested, and approved by VA prior to hosting, operation, maintenance, or use of the information system, or systems by or on behalf of VA. These security controls are to be assessed and stated within the PIA and if these controls are determined not to be in place, or inadequate, a POA&M must be submitted and approved prior to the collection of PII.Outsourcing (Contractor facility, Contractor equipment or Contractor staff) of systems or network operations, telecommunications services, or other managed services requires certification and accreditation (authorization) (C&A) of the Contractor’s systems in accordance with VA Handbook 6500.3, Certification and Accreditation and/or the VA OCS Certification Program Office. Government-owned (Government facility or Government equipment) Contractor-operated systems, third party or business partner networks require memorandums of understanding and interconnection agreements (MOU-ISA) which detail what data types are shared, who has access, and the appropriate level of security controls for all systems connected to VA networks.The Contractor/Subcontractor’s system must adhere to all FISMA, FIPS, and NIST standards related to the annual FISMA security controls assessment and review and update the PIA. Any deficiencies noted during this assessment must be provided to the VA contracting officer and the ISO for entry into VA’s POA&M management process. The Contractor/Subcontractor must use VA’s POA&M process to document planned remedial actions to address any deficiencies in information security policies, procedures, and practices, and the completion of those activities. Security deficiencies must be corrected within the timeframes approved by the Government. Contractor/ Subcontractor procedures are subject to periodic, unannounced assessments by VA officials, including the VA Office of Inspector General. The physical security aspects associated with Contractor/Subcontractor activities must also be subject to such assessments. If major changes to the system occur that may affect the privacy or security of the data or the system, the C&A of the system may need to be reviewed, retested and re-authorized per VA Handbook 6500.3. This may require reviewing and updating all of the documentation (PIA, System Security Plan, and Contingency Plan). The Certification Program Office can provide guidance on whether a new C&A would be necessary.The Contractor/Subcontractor must conduct an annual self assessment on all systems and outsourced services as required. Both hard copy and electronic copies of the assessment must be provided to the COR. The Government reserves the right to conduct such an assessment using Government personnel or another Contractor/ Subcontractor. The Contractor/Subcontractor must take appropriate and timely action (this can be specified in the contract) to correct or mitigate any weaknesses discovered during such testing, generally at no additional cost.VA prohibits the installation and use of personally-owned or Contractor/ Subcontractor owned equipment or software on VA’s network. If non-VA owned equipment must be used to fulfill the requirements of a contract, it must be stated in the service agreement, SOW or contract. All of the security controls required for Government furnished equipment (GFE) must be utilized in approved other equipment (OE) and must be funded by the owner of the equipment. All remote systems must be equipped with, and use, a VA-approved antivirus (AV) software and a personal (host-based or enclave based) firewall that is configured with a VA approved configuration. Software must be kept current, including all critical updates and patches. Owners of approved OE are responsible for providing and maintaining the anti-viral software and the firewall on the non-VA owned OE.All electronic storage media used on non-VA leased or non-VA owned IT equipment that is used to store, process, or access VA information must be handled in adherence with VA Handbook 6500.1, Electronic Media Sanitization upon: (i) completion or termination of the contract or (ii) disposal or return of the IT equipment by the Contractor/Subcontractor or any person acting on behalf of the Contractor/ Subcontractor, whichever is earlier. Media (hard drives, optical disks, CDs, back-up tapes, etc.) used by the Contractors/Subcontractors that contain VA information must be returned to VA for sanitization or destruction or the Contractor/Subcontractor must self-certify that the media has been disposed of per 6500.1 requirements. This must be completed within 30 days of termination of the contract.Bio-Medical devices and other equipment or systems containing media (hard drives, optical disks, etc.) with VA sensitive information must not be returned to the vendor at the end of lease, for trade-in, or other purposes. The options are:Vendor must accept the system without the drive;VA’s initial medical device purchase includes a spare drive which must be installed in place of the original drive at time of turn-in; orVA must reimburse the company for media at a reasonable open market replacement cost at time of purchase.Due to the highly specialized and sometimes proprietary hardware and software associated with medical equipment/systems, if it is not possible for VA to retain the hard drive, then;The equipment vendor must have an existing BAA if the device being traded in has sensitive information stored on it and hard drive(s) from the system are being returned physically intact; andAny fixed hard drive on the device must be non-destructively sanitized to the greatest extent possible without negatively impacting system operation. Selective clearing down to patient data folder level is recommended using VA approved and validated overwriting technologies/methods/tools. Applicable media sanitization specifications need to be preapproved and described in the purchase order or contract.A statement needs to be signed by the Director (System Owner) that states that the drive could not be removed and that (a) and (b) controls above are in place and completed. The ISO needs to maintain the documentation.SECURITY INCIDENT INVESTIGATIONThe term “security incident” means an event that has, or could have, resulted in unauthorized access to, loss or damage to VA assets, or sensitive information, or an action that breaches VA security procedures. The Contractor/Subcontractor shall immediately notify the COR and simultaneously, the designated ISO and Privacy Officer for the contract of any known or suspected security/privacy incidents, or any unauthorized disclosure of sensitive information, including that contained in system(s) to which the Contractor/Subcontractor has access.To the extent known by the Contractor/Subcontractor, the Contractor/Subcontractor’s notice to VA shall identify the information involved, the circumstances surrounding the incident (including to whom, how, when, and where the VA information or assets were placed at risk or compromised), and any other information that the Contractor/Subcontractor considers relevant.With respect to unsecured protected health information, the business associate is deemed to have discovered a data breach when the business associate knew or should have known of a breach of such information. Upon discovery, the business associate must notify the covered entity of the breach. Notifications need to be made in accordance with the executed business associate agreement.In instances of theft or break-in or other criminal activity, the Contractor/ Subcontractor must concurrently report the incident to the appropriate law enforcement entity (or entities) of jurisdiction, including the VA OIG and Security and Law Enforcement. The Contractor, its employees, and its Subcontractors and their employees shall cooperate with VA and any law enforcement authority responsible for the investigation and prosecution of any possible criminal law violation(s) associated with any incident. The Contractor/Subcontractor shall cooperate with VA in any civil litigation to recover VA information, obtain monetary or other compensation from a third party for damages arising from any incident, or obtain injunctive relief against any third party arising from, or related to, the incident.LIQUIDATED DAMAGES FOR DATA BREACHConsistent with the requirements of 38 U.S.C. §5725, a contract may require access to sensitive personal information. If so, the Contractor is liable to VA for liquidated damages in the event of a data breach or privacy incident involving any SPI the Contractor/Subcontractor processes or maintains under this contract.The Contractor/Subcontractor shall provide notice to VA of a “security incident” as set forth in the Security Incident Investigation section above. Upon such notification, VA must secure from a non-Department entity or the VA Office of Inspector General an independent risk analysis of the data breach to determine the level of risk associated with the data breach for the potential misuse of any sensitive personal information involved in the data breach. The term 'data breach' means the loss, theft, or other unauthorized access, or any access other than that incidental to the scope of employment, to data containing sensitive personal information, in electronic or printed form, that results in the potential compromise of the confidentiality or integrity of the data. Contractor shall fully cooperate with the entity performing the risk analysis. Failure to cooperate may be deemed a material breach and grounds for contract termination.Each risk analysis shall address all relevant information concerning the data breach, including the following:Nature of the event (loss, theft, unauthorized access);Description of the event, including:date of occurrence;data elements involved, including any PII, such as full name, social security number, date of birth, home address, account number, disability code;Number of individuals affected or potentially affected;Names of individuals or groups affected or potentially affected;Ease of logical data access to the lost, stolen or improperly accessed data in light of the degree of protection for the data, e.g., unencrypted, plain text;Amount of time the data has been out of VA control;The likelihood that the sensitive personal information will or has been compromised (made accessible to and usable by unauthorized persons);Known misuses of data containing sensitive personal information, if any;Assessment of the potential harm to the affected individuals;Data breach analysis as outlined in 6500.2 Handbook, Management of Security and Privacy Incidents, as appropriate; andWhether credit protection services may assist record subjects in avoiding or mitigating the results of identity theft based on the sensitive personal information that may have been compromised.Based on the determinations of the independent risk analysis, the Contractor shall be responsible for paying to the VA liquidated damages in the amount of $37.50 per affected individual to cover the cost of providing credit protection services to affected individuals consisting of the following:Notification;One year of credit monitoring services consisting of automatic daily monitoring of at least 3 relevant credit bureau reports;Data breach analysis;Fraud resolution services, including writing dispute letters, initiating fraud alerts and credit freezes, to assist affected individuals to bring matters to resolution;One year of identity theft insurance with $20,000.00 coverage at $0 deductible; andNecessary legal expenses the subjects may incur to repair falsified or damaged credit records, histories, or financial affairs.SECURITY CONTROLS COMPLIANCE TESTINGOn a periodic basis, VA, including the Office of Inspector General, reserves the right to evaluate any or all of the security controls and privacy practices implemented by the Contractor under the clauses contained within the contract. With 10 working-day’s notice, at the request of the Government, the Contractor must fully cooperate and assist in a Government-sponsored security controls assessment at each location wherein VA information is processed or stored, or information systems are developed, operated, maintained, or used on behalf of VA, including those initiated by the Office of Inspector General. The Government may conduct a security control assessment on shorter notice (to include unannounced assessments) as determined by VA in the event of a security incident or at any other time. TRAININGAll Contractor employees and Subcontractor employees requiring access to VA information and VA information systems shall complete the following before being granted access to VA information and its systems:Sign and acknowledge (either manually or electronically) understanding of and responsibilities for compliance with the Contractor Rules of Behavior, Appendix D relating to access to VA information and information systems;Successfully complete the VA Privacy and Information Security Awareness and Rules of Behavior training and annually complete required security training;Successfully complete Privacy and HIPAA Training if Contractor will have access to PHI;Successfully complete the appropriate VA privacy training and annually complete required privacy training; andSuccessfully complete any additional cyber security or privacy training, as required for VA personnel with equivalent information system access The Contractor shall provide to the contracting officer and/or the COR a copy of the training certificates and certification of signing the Contractor Rules of Behavior for each applicable employee within 1 week of the initiation of the contract and annually thereafter, as required.Failure to complete the mandatory annual training and sign the Rules of Behavior annually, within the timeframe required, is grounds for suspension or termination of all physical or electronic access privileges and removal from work on the contract until such time as the training and documents are complete.ADDENDUM C - REQUEST FOR INFORMATION (RFI) QUESTIONS)A.Does industry recommend utilizing existing commercial-off-the-shelf (COTS) based Governance, Risk, and Compliance (GRC) Solutions for use as part of Information Security Continuous Monitoring (ISCM) versus a homegrown solution? Considering the areas of Analysis/Risk Scoring Subsystem (A/RSS), multi-layered dashboards, risk correlation and multidimensional risk analysis, Database Sub-Systems (DBSS), Presentation/ Reporting Subsystem (P/RSS), Inventory Subsystem (ISS), continuous monitoring (CM) for Federal Information Security Management Act (FISMA) audit compliance, Security Content Automation Protocol (SCAP) management, connector feeds to existing systems, along with other requirements as detailed in the RFI?Also provide supporting rationale including advantages and disadvantages.How does your solution address the recommendations and guidance in National Institute of Standards and Technology (NIST) Interagency Report (IR), NIST IR 7756, CAESARS Framework Extension: An Enterprise Continuous Monitoring Technical Reference Model (Second Draft)? Specifically, detail how your solution matches up against NIST IR 7756 (Second draft), Figures 2 through 10. In part, this should be done by including the figures in your response and indicating each element your solution addresses.C.Please provide cost estimates for a GRC Solution, to include options for a phased in, scaled up approach to add features/modules as budget and project development time allows. Include cost of connectors to VA’s existing systems and tools, applications, risk scoring engine for an A/RSS, implementation of the COTS solution, training, and customization options.D.List the hardware requirements (minimum, recommended, and peak performance), as well as other required elements such as network connectivity for each proposed solution.E.If proposing more than one solution outline which is your recommended solution considering the size and complexity of VA. (please note VA has over 600 systems, over 1,500 facilities, and over 350,000 workstations.)F.Are there any yearly recurring costs for administrative support and/or software maintenance over and above the initial cost of the GRC Solution? If so, please provide these options in detail so all required and optional cost for follow-on years can be understood and budgeted.G.What options do you provide for acquiring the software such as perpetual licenses, software as a service offerings, etc? Outline the costs for any such options.H.Has your GRC Solution been deployed at other federal agencies?If so, detail which agencies, what type of deployment (such as ISCM), and a list a point of contact (POC) for each.I.Has your GRC Solution been deployed in a network where it was required to go through an Assessment and Authorization (A&A) process? If so, which agency was this done with and what FISMA level was the system scored against (low, medium, or high)?J.If your COTS solution has never gone through and received an authority to operate (ATO) in a FISMA compliant environment, what processes and or preliminary work have you completed which would indicate the possible success of meeting a required FISMA certification?K.What are your options for onsite staff to assist with GRC Solution support for primary enterprise software, applications, connectors, and all elements for integration and implementation?List several options to include two staff members onsite for base year.L.What are your options for onsite training for users and admin staff? List several options to include two months of onsite support.M.What are your options for remote computer based training (CBT) for users? List several options to include 1 year of CBT.N.What are your options for ISCM/risk Management Framework (RMF)/Risk Management (RM)/GRC business process analysis consultants? Options for 1 or 2 personnel for 4, 6, and 8 months.O.What is your GRC Solutions’ level of 508 compliance.P.Does your GRC Solution address the six elements of the NIST RMF (Categorize, Select, Implement, Assess, Authorize, and Monitor)? If yes, describe how.Q.To what extent is your GRC Solution offering compliant with: SCAP, Open Vulnerability and Assessment Language (OVAL), Common Configuration Enumeration (CCE), Common Vulnerability Enumeration (CVE), Common Platform Enumeration (CPE), Extensible Configuration Checklist Description Format (XCCDF), Common Vulnerability Scoring System (CVSS), Common Weakness Scoring System (CWSS), and other standards referenced in this PWS.R.State what type of Service Level Agreement (SLA) your GRC Solution provides.S.Can your proposed GRC Solution meet all existing VA polices? T.What type of continuing support can you provide after an award is made and at what cost?U.If VA procured an internal e-discovery, archiving, or records management solution how would this interface with and control the data in the GRC Solution’s DBSS? V.What options does your GRC Solution have which can provide access control to VA information with and without the use of 3rd party software such as Citrix type virtual private network (VPN) solution on a mobile or non-government furnished equipment (GFE) device?W.What are the storage limits of each element of the GRC Solution? How are they controlled?X.Provide a redacted (where required) actual contract including costs for another government agency that has contracted with your company for a similar GRC Solution.Y.Would there need to be any special services (hardware, software, cost) involved concerning the use of any mobile device and your GRC Solution?Z. Please identify if you are currently a contract holder on any Federal Contract Vehicle. For example, National Aeronautics and Space Administration (NASA) Solutions for Enterprise-Wide Procurement (SEWP) Government-Wide Acquisition Contract (GWAC), U.S. General Services Administration (GSA), Transformation Twenty-One Total Technology (T4) etc.ADDENDUM D (Acronym List)See Attached: NIST IR 7298, rev. 1, Glossary of Key Information Security Terms, February 2011.ADDENDUM E (ISCM CONOPS -- Data Flow and Security Architecture)\sADDENDUM F (GRC Solution Requirements Spreadsheet)ADDENDUM G (Risk Management CONOPS Overview DRAFT) ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download