FY19 Requirement Justification Funding Request (RJFR) - F5 SCCA Cloud Gateway

Aug 31, 2026

Upload by Paura

FY19 Requirement Justification Funding Request (RJFR) outlines the rationale for deploying an F5 SCCA Cloud Gateway to support DoD organizations moving workloads to commercial public cloud providers. The request explains DISA SCCA 2017 objectives, detailing the BCAP, VDSS, VDMS, and TCCM components and how F5 BIG-IP Virtual Editions templates map to required security functions. It also addresses organizational impact, compliance goals, and provides an initial cost and funding approach for purchasing and first-year support.

LanguageEnglish

CategoryLetters

FormatDOCX

Pages8

Reading Time3 min

AccessFree to download

FY19 Requirement Justification Funding Request (RJFR)

Background and Description of SCCA Requirements

SCCA Components and Their Purposes

Mapping SCCA to Cloud and F5 Capabilities

Impact on Organization and Cost Estimate

Funding Request Details

FY19 Requirement Justification Funding Request (RJFR) F5 SCCA Cloud Gateway Background: DISA has established a set of security standards for DoD Organization intent on moving workloads to Commercial Public Cloud Providers. The guidance is defined as the HYPERLINK "https://iasecontent.disa.mil/stigs/pdf/SCCA_FRD_v2-9.pdf" Secure Cloud Computing Architecture (SCCA) published in 2017. SCCA describes the functional objectives for securing the Defense Information System Network’s (DISN) and Commercial Cloud Provider connection points with the end goal of providing mission owners secure cloud applications and the ability to engage public cloud providers directly. Description of the Requirements: There are four components to the SCCA: Boundary Cloud Access Point (BCAP) Virtual Datacenter Security Stack (VDSS) Virtual Datacenter Services (VDMS) Trusted Cloud Credential Manager (TCCM) Cloud Service Providers (CSP’s) like Microsoft, AWS and Google are all developing solutions that enable workloads and applications to run in the cloud. These cloud-based applications must meet the security standards defined by the SCCA. The VCAP, VDSS, and VDMS requirements are not specific to a cloud provider and can be delivered by the responsible DoD application or mission owners. F5 BIG-IP Virtual Editions (VE) provide cloud-based applications with the security capabilities required by the SCCA. The joint architecture between F5 and CSP’s aims to develop a holistic cloud architecture that bring together and satisfy every functional objective of SCCA for DoD cloud workloads. As a Mission Owner it is critical that we address these requirements. SCCA Solution Template F5 SCCA functionality is deployed through the use of templates. These templates are fielded via the Cloud Service Provider and the F5 BIG-IP Virtual Edition (VE). The template deployment is focused on the VDSS, BCAP, and VDMS components. The Mission Owner environments will not be deployed as part of these templates but there are additional scripts for deploying and attaching a Mission Owners application in IL5, IL4, etc. Mission Owner application environments will be customized for the unique application requirements. The below paragraphs describe the components of SCCA in more detail. Boundary Cloud Access Point (BCAP) The purpose of the BCAP is to protect the DISN from attacks originating in the cloud environment. BCAP will perform intrusion detection and prevention as well as filter out unauthorized traffic. This component can be co-located with other components of the SCCA. Virtual Datacenter Security Stack (VDSS) The purpose of the VDSS is to protect DoD Mission Owner applications that are hosted in Azure. VDSS performs the bulk of the security operations in the SCCA. It will conduct traffic inspection in order to secure the applications running in Azure. This component can be provided within your cloud environment. Virtual Datacenter Services (VDMS) The purpose of VDMS is to provide host security as well as shared data center services. The functions of VDMS can either run in the hub of your SCCA or the Mission Owner can deploy pieces of it in their own specific Azure subscription. This component can be provided within your cloud environment. Trusted Cloud Credential Manager (TCCM) TCCM is a business role. This individual will be responsible for managing the SCCA. Their duties include establishing plans and policies for account access to the cloud environment, ensuring identity and access management is operating properly, and to maintain the Cloud Credential Management Plan. This individual is appointed by the Authorizing Official. The BCAP, VDSS, and VDMS will provide the capabilities needed for the TCCM to perform their job function. Mapping SCCA to Cloud and F5 Capabilities The following tables illustrate the mapping of native Microsoft Azure Cloud services and capabilities of F5 BIG-IP virtual appliances to the SCCA guidance for BCAP, VDSS and VDMS. Descriptions for the

FAQs

What is the DISA SCCA and why is it important for DoD cloud adoption?

SCCA (2017) defines functional objectives to secure Defense Information System Network connection points with commercial cloud providers. It enables mission owners to run secure cloud applications and directly engage public cloud providers while maintaining required security standards.

What are the four key SCCA components covered in this request?

The document describes BCAP, VDSS, VDMS, and TCCM. BCAP protects against cloud-origin attacks, VDSS performs core security operations for applications hosted in Azure, VDMS provides host security and shared datacenter services, and TCCM is the business role responsible for managing SCCA-related account access and credentials.

How does F5 SCCA Cloud Gateway relate to Azure and cloud service providers?

The request states that F5 BIG-IP Virtual Editions provide security capabilities aligned to SCCA objectives through template deployment. It emphasizes that VDSS, BCAP, and VDMS template deployment is handled via the cloud service provider and F5 VE, while mission owner environments are customized for specific application needs.

Aug 31, 2026

Upload by Paura