SE2 Technical Data.pdf
PDF 756 KB Posted
- Attached to
- CECOM Unified Services Support Federal contract opportunity
- Solicitation number
- W56JSR-22-R-UniServ
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| (draft) Labor Categories (LCATs) and Level Of Effort (LOE)-Unified Tech Services.xlsx | XLSX spreadsheet | |
| Market Research Narrative-Unified Tech Services_Round2.docx | DOCX document | |
| SE2 Tools.pdf | ||
| Planned 1st Year Task Orders-Unified Tech Services.docx | DOCX document | |
| (draft) CDRLs-Unified Tech Services.docx | DOCX document | |
| Planned SE2 Infrastructure Task Order-Unified Tech Services.docx | DOCX document | |
| (draft) Performance Work Statement-Unified Tech Service Base IDIQ (v3).docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SE2 Additional Details As of June 2022
Accessibility NIPR and DREN VPN capability NIPR laptops or desktops DREN laptops using SE2 image
Usage SE2 User Accounts: 1,230 Number of Projects: 227
Classification Unclassified Impact Level 4
Environment SE2 currently all hosted at SEC Future expansion to Hybrid Cloud Solution
Hardware 76 Network devices (Switches, routers, firewalls) 583 machines on the Dev segment 120 machines on the Test segment 207 Virtual Servers 28 of Databases
Authority to Operate Authorizing Official: DEVCOM
ATD: 12/15/2023
Type Authorization - No Impact - Moderate System Type - IS Enclave
SE2 On-Premise Network Diagram
DREN
SEC
AWS GovCloud
C5ISR
CECOM SEC SE2 Hybrid Cloud Solution The AWS GovCloud and Azure Gov network segments will be a logical extension of the current SEC on-prem network segments, similar to when we add another SEC building at APG. No traffic is routed over the Internet or outside the boundary. If a system/service within the Cloud network segment needs to communicate with another system/service that traffic would go through the normal security/routing stacks just like an on-prem system/service. This is achieved by:
• DREN will create an AWS Direct Connect circuit within SEC’s AWS subscription using an “on-prem” /24 subnet (/23 preferred) identified by C5ISR & SEC.
• DREN will create an Azure Express Route circuit within SEC’s Azure subscription using an “on-prem” /24 subnet (/23 preferred) identified by C5ISR & SEC.
• DREN will create a trusted VLAN connection between each authorized Cloud Service Provider (CSP) circuit and the DREN Service Delivery Point (SDP) at APG.
• C5ISR will change the SEC connection from an access port to a trunk point with 3 VLANs: as-is traffic, plus the 2 trusted VLANs.
• SEC will create a private BGP peering with Azure and AWS using the 169.254.x.x link-local addresses provided by DREN and announce only the default route
(0.0.0.0).
• All infrastructure services (HBSS, ACAS, AD, SCCM,…) will continue to work as expected with AWS/Azure based resources/services.
AWS and Azure are FedRAMP compliant and have DISA Provisional Authorities. This is the CSP version of an RMF ATO and they have inheritable eMASS records.
DREN
SEC
AWS GovCloudC5ISR
Logical Overview
Physical Overview
PaaS IaaSIaaSIaaSIaaSPaaS
| SEC Hybrid Cloud-v2.pdf |
| SEC Hybrid Cloud-v2.vsdx |
| Overview |
| SE2 Technical Data |
| SE2 data |
| SE2 Network Production Diagram 20220721v2_reduced.pdf |
File details come from the government source that posted it. Updated .