1 / 29

Submarine Assessment of Strike Over Secret with post meeting changes 2/06

Submarine Assessment of Strike Over Secret with post meeting changes 2/06. PURPOSE. Convey SSN Secret Over Strike Impacts and Solution Options To Support Navy Decision On Tomahawk Weapon System Road Ahead. KEY SOLUTION GOALS.

ruana
Download Presentation

Submarine Assessment of Strike Over Secret with post meeting changes 2/06

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Submarine Assessment of Strike Over Secretwith post meeting changes2/06

  2. PURPOSE • Convey SSN Secret Over Strike Impacts and Solution Options To Support Navy Decision On Tomahawk Weapon System Road Ahead

  3. KEY SOLUTION GOALS • Provide Flexible IP Based Comms For all TWS Participants at SECRET Level • Retain Submarine Independent or Battle Group Support Mission Profiles • Retain Submarine Concurrent SCI and Strike Missions Capability • Retain Submarine Capability to Receive Strike Comms in EMCON State • Identify All Potential Solutions To Support Best Value Decision

  4. SSN Solution Tree SECRET Strike Data GENSER?; (Not SPECAT / LIMDIS) SPECAT / LIMDIS ? Surface Strike INE Retained? Is S/W Encryption Required? SSN Has IP Down-Hull? NO NO Start Here NO 4 Med/High Cost # = Solution Number YES YES PRE-TI-04 SSNs Add New Strike S/W Encryption &Keep Sneaker-Net YES 8 Med Cost GENSER SSN Has IP Down-Hull? Surface Strike INE Retained? TI-04 SSNs Add S/W Encryption To MDS; Only Connect Strike LAN To Enclave Guard NO NO NO ? SSN Has IP Down-Hull? Is NO IP Acceptable? YES NO YES Auto Bridge INE to SIPRNET Feasible? Auto Bridge INE to SSN TS Enclave Feasible? NO Is NO IP Acceptable? SSN Has IP Down-Hull? NO NO NO NO YES YES YES YES YES YES Low Cost 1 SSN Has IP Down-Hull? SSN Has IP Down-Hull? PRE-TI-04 SSNs Uses Legacy Comms; No Back-Up IP NO NO 3 7 YES 5 2 6 YES 9 High Cost Low Cost Med Cost High Cost Low Cost Low Cost TI-04 SSNs Connect Strike LAN To SUBLAN Vice TS Enclave Pre-TI-04 SSNs Add New Strike INE; Connect To SECRET Strike LAN TI-04 SSNs Add New Strike INE; Connect To SECRET Strike LAN Pre-TI-04 SSNs Use Existing SECRET ISDS & Sneaker-Net TI-04 SSNs Leave Strike LAN Connected To TS Enclave Pre-TI-04 SSNs Use Existing TS ISDS & Sneaker-Net

  5. Pre-TI-04 SSN SOLUTIONS • Use Legacy Comms Circuits; No IP Comms • 688/688I(EHF, UHF Serial); • IP Just a Back-up for the Legacy Circuits on These Boats • SSN21,23(EHF Serial)Post Mtg Note: The only Boat to consider here is the 21 it will be deployed late ’06 before TI-04 modernization; the 23 will get TI-04 before deploying in the secret strike era so is not an issue for the pre-TI04 case: IF we can rely on EHF direct for the 21’s Deployment this year then it will get the TI-04 solution in ’07 and we can avoid making pre-TI-04 changes to any Sewaolf Class; • Not Applicable for Virginia Post PSA • No EHF/UHF on Virginia Post PSA • External IP Bridge: Strike-INE Enclave and SSN TS Enclave ISDS • IA Acceptability and STT Update TBD • External IP Bridge: Strike-INE Enclave and SSN SIPRNET ISDS • IA Acceptability and STT Update TBD • External IP Bridge: Strike-INE Enclave and SSN Secret ISDS/MDS Covered by Software Based Encryption • IA Acceptability and STT Update TBD • Would Add S/W Encryption Tool to Either SUBLAN Node or TS Enclave Node If Possible; If Not - It Requires Another Enclave Like Option 5. • Implement New SSN Strike-INENetwork Enclave In Radio Room • New ADNS Connection; Router & ISDS/MDS Terminal • Could This Be a Carry-on or TempAlt in Near Term? Could Use For Option #1 Also • Still Sneaker-Net From ISDS/MDS to CCS/ATWCS/TTWCS

  6. TI-04 SSN SOLUTIONS • External IP Bridge: Strike-INE Enclave and SSN TS Enclave ISDS • IA Acceptability and STT Update TBD • External IP Bridge: Strike-INE Enclave and SSN SUBLAN / SIPRNET • IA Acceptability and STT Update TBD • External IP Bridge: Strike-INE Enclave and SSN Secret ISDS/MDS Covered by Software Based Encryption • IA Acceptability and STT Update TBD • Would Add S/W Encryption Tool to Node in Strike LAN; Connect Strike LAN to Either SUBLAN Enclave Guard. • Implement New SSN Strike-INE Network Enclave • Sub-Options: • Radio Room Hosts New Network Enclave INE • Connect ADNS to New INE to Strike LAN • CCS Hosts New Network Enclave INE • Connect SUBLAN to New INE to Strike LAN

  7. IA Questions • Can We Avoid H/D Swap-out For Pre-TI-04 Boats’ Strike Downgrade to Secret? • Hardware Not Directly Connected to TS Enclave • Hosted Strike Data Now Deemed Secret • Is an Automated External IP Bridge Between Surface Ship Strike-INE Enclave and SSN TS Enclave ISDS Possible? • Manual Bridge Would Not Provide Quality of Service Required • Is an Automated External IP Bridge Between Surface Ship Strike-INE Enclave and SSN SIPRNET/SUBLAN ISDS Possible? • Manual Bridge Would Not Provide Quality of Service Required • Is an Automated External IP Bridge Between Surface Strike-INE Enclave and SSN Secret ISDS/MDS Covered by New Software Based Encryption Possible? • What are SPECAT / LIMDIS Requirements for Data Segregation? • Can it be Sent in Clear on SIPRNET? Is Type II Encryption OK? • On TI-04 Boats Can it Be Mingled with Secret Network Enclaves?

  8. Pre-TI-04 SOLUTION 1 • Use Legacy Comms Circuits; No IP Comms • 688/688I(EHF, UHF Serial); • IP Just a Back-up for the Legacy Circuits on These Boats • SSN21,23(EHF Serial)Post Mtg Note: The only Boat to consider here is the 21 it will be deployed late ’06 before TI-04 modernization; the 23 will get TI-04 before deploying in the secret strike era so is not an issue for the pre-TI04 case: IF we can rely on EHF direct for the 21’s Deployment this year then it will get the TI-04 solution in ’07 and we can avoid making pre-TI-04 changes to any Sewaolf Class; • Not Applicable for Virginia Post PSA • No EHF/UHF on Virginia Post PSA • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or • Replaced or Scrubbed in Diskwasher • Impacts: • Potentially Boats Get New Strike Media • Reduction of Comms Capability; Change to Comms Procedures • Costs: 350K • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K: This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • Schedule: • 2yrs If Hard Disk Replacement Needed • Nearly Immediately If Disks Can Be Reclassified In Place • H/D Replacement on Deployment Allowed ~1yr; but Higher Labor/Travel Cost • Risk:

  9. Pre-TI-04 SOLUTION 2 • External IP Bridge: Strike-INE Enclave and SSN TS Enclave ISDS 688/688I/Virginia/Seawolf • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher; As in Option 1 • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and SSN TS Enclave. • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • Impacts: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher • Costs: 350+STT • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • Bridge Sites: TDB • Schedule: • 2yrs If Hard Disk Replacement Needed • SSN Nearly Immediately If Disks Can Be Reclassified In Place • SSN H/D Replacement on Deployment Allowed ~1yr; but Higher Labor/Travel Cost • Bridge Sites: TBD • Risk: • IA Acceptability • Dependence on Bridge to Pass Data

  10. Pre-TI-04 SOLUTION 3 • External IP Bridge: Strike-INE Enclave and SSN Secret Enclave ISDS; 688/688I/Virginia/Seawolf • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher; As in Option 1 • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and SSN Secret Enclave. • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • Impacts: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher • Minor Change to Comms Procedure; Data Received in Secret vs TS Enclave • Costs: 350+STT • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • Bridge Sites: TDB • Schedule: • 2yrs If Hard Disk Replacement Needed • SSN Nearly Immediately If Disks Can Be Reclassified In Place • SSN H/D Replacement on Deployment Allowed ~1yr; but Higher Labor/Travel Cost • Bridge Sites: TBD • Risk: • IA Acceptability • Dependence on Bridge to Pass Data

  11. Pre-TI-04 SOLUTION 4 • External IP Bridge: Strike-INE Enclave and SSN Secret ISDS/MDS Covered by Software Based Encryption 688/688I/Virginia/Seawolf • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher; As in Option 1 • Add S/W Encryption Tool to Either SUBLAN Node or TS Enclave Node If Possible; • If Not - It Requires Another Enclave To Host Encryption Tools and Enclave Like Option 5. • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and New S/W Encryption • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • Impacts: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher • Minor Change to Comms Procedure; Data Received in Strike vs TS Enclave • Update Required to SSAA Due to Reliance on S/W Encryption Tool • Costs: 450K+STT • If New SSN Enclave Required, Cost Impact High, About the Same As Option5 • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • SSAA: 100K • Bridge Sites: TDB • Schedule: • 5yrs If New Enclave Required - Otherwise; • 2yrs If Hard Disk Replacement Needed • SSN Nearly Immediately If Disks Can Be Reclassified In Place • SSN H/D Replacement on Deployment Allowed ~1yr; but Higher Labor/Travel Cost • Bridge Sites: TBD • Risk: • IA Acceptability • S/W Encryption Tool Integration • Dependence on Bridge to Pass Data

  12. Pre-TI-04 SOLUTION 5See additional post mtg note next page • Implement New SSN Strike-INE Network Enclave In Radio Room 688/688I/Virgina Post PSA • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher; As in Option 1 • Add New Strike INE Enclave In Radio; INE, Router, ISDS (to retain EMCON Comms); • Impacts: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher • Minor Change to Comms Procedure; Data Received in Strike vs TS Enclave • Update Required to SSAA • Costs: Not Vetted With SPAWAR Yet: 9.6M • 688/688I/Virgina NRE For New Radio Enclave: 5M • 42 Boats’ RE: 100K each: 4.2M; It was discussed that this boat count could be reduced See additional post mtg note next page • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • SSAA: 100K • Schedule: • 3-5yrs For New Enclave; • 2yrs If Hard Disk Replacement Needed • SSN Nearly Immediately If Disks Can Be Reclassified In Place • SSN H/D Replacement on Deployment Allowed ~1yr; but Higher Labor/Travel Cost • Risk:

  13. Pre-TI-04 SOLUTION 5 Post Mtg Note • Implement New SSN Strike-INE Network Enclave In Radio Room 688/688I/Virgina Post PSA • Description: • Boats’ Strike Processing Element Hard Disks Either Designed as Secret Due to Reclassification or Replaced or Scrubbed in Diskwasher; As in Option 1 • Add New Strike INE Enclave In Radio; INE, Router, ISDS (to retain EMCON Comms); • Post Note: • The discussion at the meeting centered on the fact that not all 42 boats in this solution class would benefit the same from re-gaining the secret strike IP comms after the transition. The suggestion was that perhaps the pre-TTWCS boats would not benefit enough from changes to get the secret strike IP Comms back. • They currently rely on legacy circuits EHF/UFH Hewits/BGIXS to get strike comms. • Pre-TTWCS boats use paper ESPs; electronic IP based ESPs aren’t used. • IP MDUs could be used a legacy path back-up. • This consideration leads to the following count change possibilities; • Back to the page 4 flow chart - the case is: ‘Start Here’ - Strike Data is Genser- INE Retained – No Bridges are feasible. • Consider that No IP Strike Comms IS acceptable for Pre-TTWCS-Pre-TI-04 (no Down-Hull IP) boats. • This could change the boat counts and cost guesses as follows: • 30 Boats representing 688 & 688I classes could be considered for NOT getting the INE Change • Shipalt numbers stay the same since 688&688I are in both TTWCS and Pre-TTWCS sets • Instead of 42 pre-TI-04 boats getting the new INE network enclave, only the 12 Pre-TI-04 TTWCS Boats get it • Costs: Not Vetted With SPAWAR Yet: 6.6M • 688/688I/Virgina NRE For New Radio Enclave: 5M • 12 Boats’ RE: 100K each: 1.2M; • 10 Hard Disks Each for 42 Boats: 150K • Team to Deliver & Install + Travel: 200K This was discussed as potentially reduced significantly if we can just mail of the drives and have the boats reload the S/W. • ILS/Employment Documentation Changes 100K • SSAA: 100K

  14. TI-04 SOLUTION 6 • External IP Bridge: Strike-INE Enclave and SSN TS Enclave ISDS 688I/Seawolf • Description: • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and SSN TS Enclave. • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • BYG-1 Strike LAN Stays Connected to SSN TS Enclave • Impacts: • TI-04 SSNs Strike Remains TS • 688I Have EFH/UFH Back-up; • 21/23 EFH Back-Up • 22 No EHF • Costs: 100K+STT • SSNs: Network Addressing Change: 100K • Bridge Sites: TDB • Schedule: • SSNs: 6-9mos; Complete Before TI-04 Deployments Start; Fall’06 • Bridge Sites: TBD • Risk: • IA Acceptability • Dependence on Bridge to Pass Data

  15. TI-04 SOLUTION 7 • External IP Bridge: Strike-INE Enclave and SSN SUBLAN/SIPRNET 688I/Seawolf • Description: • Boats’ Strike Processing Element Hard Disks Either Replaced or Scrubbed in Diskwasher; • Strike LAN Radio Connection Moved to SUBLAN • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and SSN Secret Enclave. • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • Impacts: • Boats’ Strike Processing Element Hard Disks Either Replaced or Scrubbed in Diskwasher • ShipAlt/ECP to Change Strike LAN Connection from Radio TS Enclave to SUBLAN • Minor Change to Comms Procedure; Data Received Via Secret vs TS Enclave • Costs: 700K+STTs • 688I & Seawolf ShipAlt to CCS & 688I SUBLAN/Seawolf Secret Enclave: 200K • Install On 13 Boats: 200K • SSNs Network Addressing Change: 100K • BYG-1 ILS Update: 100K • 10 Hard Disks Each for 10 Boats: 30K • Team to Deliver & Install + Travel: 75K • Bridge Sites: TDB • Schedule: • 6-9Mos; Before TI-04 Boats Deploy • Bridge Sites: TBD • Risk: • IA Acceptability • Dependence on Bridge to Pass Data As discussed in the meeting, there is an alternate sub-option; The Secret data path identified here as a new connection from SUBLAN to Strike LAN could be routed through the AN/BYG-1 Enclave guard existing path. The Radio Room TS enclave connection would still be disconnected; The cost of that change may be lower due to not needing the shipalts to CCS/SUBLAN,. Network addressing, and Enclave Guard rules set change are needed.

  16. TI-04 SOLUTION 8 • External IP Bridge: Strike-INE Enclave and SSN Secret ISDS/MDS Covered by Software Based Encryption 688I/Seawolf • Would Add S/W Encryption Tool to Node in Strike LAN; Connect Strike LAN to Either SUBLAN Enclave Guard. • Description: • Boats’ Strike Processing Element Hard Disks Either Replaced or Scrubbed in Diskwasher; • Strike LAN Radio Connection Moved to SUBLAN • Add S/W Encryption Tool to Strike LAN Node; • STT or other TC2S Site Stood-Up as An Automated Bridge Between Surface INE and New S/W Encryption • Manual Bridge Not Acceptable Due to Lack of 24/7 Service • Impacts: • Boats’ Strike Processing Element Hard Disks Either Replaced or Scrubbed in Diskwasher • ShipAlt/ECP to Change Strike LAN Connection from Radio TS Enclave to SUBLAN • Minor Change to Comms Procedure; Data Received Via Secret vs TS Enclave • Costs: 800K+STTs • 688I & Seawolf ShipAlt to CCS & 688I SUBLAN/Seawolf Secret Enclave: 200K • Install On 13 Boats: 200K • SSNs Network Addressing Change: 100K • Integrate S/W Encryption: 100K • BYG-1 ILS Update: 100K • 10 Hard Disks Each for 10 Boats: 30K • Team to Deliver & Install + Travel: 75K • Bridge Sites: TDB • Schedule: • 9-12Mos; • Bridge Sites: TBD • Risk: • IA Acceptability • S/W Encryption Tool Integration • Dependence on Bridge to Pass Data

  17. TI-04 SOLUTION 9 • Implement New SSN Strike-INE Network Enclave • Sub-Options: • Radio Hosts New Enclave INE • Connect ADNS to New INE to Strike LAN • CCS Hosts New Enclave INE • Connect SUBLAN to New INE to Strike LAN • Description: • Boats’ Strike Processing Element Hard Disks Either Replaced or Scrubbed in Diskwasher; As in Option 1 • a) Add New Strike INE Enclave In Radio; INE, Router, ISDS (to retain EMCON Comms); • b) Add New Strike INE Enclave In Strike LAN; INE, ISDS (to retain EMCON Comms); Potentially Re-Host TCIP/MDS to Make Room For ISDS. • Impacts: • Boats’ Strike Processing Element Hard Disks Replaced or Scrubbed in Diskwasher • Minor Change to Comms Procedure; Data Received Via Strike vs TS Enclave • Update Required to SSAA • a) Costs: Host INE In Radio Room: Not Vetted With SPAWAR Yet: 4.6M • 688ISeawolf NRE For New Radio Enclave: 3M • 13 Boats’ RE: 100K each: 1.3M • 10 Hard Disks Each for 10 Boats: 30K • Team to Deliver & Install + Travel: 100K • SSAA: 200K • b) Costs: Host INE & ISDS in CCS: 2.4M • 688I & Seawolf NRE CCS & 688I SUBLAN/Seawolf Secret Enclave: 1M • Install On 13 Boats: 650K • SSNs Network Addressing Change: 100K • Integrate INE & ISDS Integration: 150K • BYG-1 ILS Update: 150K • 10 Hard Disks Each for 10 Boats: 30K • Team to Deliver & Install + Travel: 100K • SSAA: 200K • Schedule: • a) 2-3yr • b) 1-2yr • Risk: • a) INE Mounting in Enclave Guard MFS May Not Be Possible: Space Is Available But Access to Load Keys and Observe TACLAN Indicators Very Limited. TCIP/MDS Co-Host Concept Proven for TI-06. Switched these

  18. Platform Configurations • 688/688I Pre-TI-04 • EHF serial MDU path • TS IP EMCON MDU ISDS sneaker net path • Currently EHF serial to GFCPII or TCIP or Sneaker net from ISDS for IP • UHF serial available • 688/688I TI-04 and newer • EHF serial MDU path • TS IP EMCON MDU ISDS • TS IP MDU via PC-MDS • UHF serial available • Seawolf Class 21/23 CSRR • EHF serial MDU path • TS IP EMCON MDU ISDS • TS IP MDU via PC-MDS/Repeat • Current plans are to remove EHF serial connection in the near future, requires action to maintain this connection if needed

  19. Platform Configurations cont. • Seawolf Class 22 - TI-04 & CSRR • TS IP EMCON MDU ISDS • TS IP MDU via PC-MDS • No serial UHF/EHF path • Virginia Class Post PSA – TI-02 & CSRR • TS IP EMCON MDU ISDS • TS IP MDU via Enclave Guard to Architecture LAN to Strike • No serial UHF/EHF path • SSGN – TI-04 & CSRR • TS IP EMCON MDU ISDS • TS IP MDU via PC-MDS AWCS • No serial UHF/EHF path

  20. SIPRNET Baseline TWS End to End IP COMMS With TI-04 SSN NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router STT RF TS Router FRU TS Router SUBLAN TCIP TCIP ISDS COMM MDS Router Strike LAN Enclave Guard MDS TTWCS ISDS MSN TCIP MDS TCIP TTWCS TS Strike Key Loaded TACLANE INE MDS

  21. SIPRNET Sneaker-Net Solution 1 TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF FRU TS Router TCIP TS Router SUBLAN MDS Router TCIP ISDS COMM TTWCS MDS ISDS MSN TCIP TS Strike Key Loaded TACLANE INE Strike LAN MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  22. SIPRNET Sneaker-Net Solution 2 TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF FRU TS Router TCIP TS Router SUBLAN MDS Router TCIP ISDS COMM TTWCS MDS ISDS MSN TCIP Bridge TS Strike Key Loaded TACLANE INE Strike LAN MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  23. SIPRNET Sneaker-Net Solution 3 TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF FRU TS Router TCIP TS Router SUBLAN MDS Router TCIP ISDS COMM TTWCS MDS ISDS MSN TCIP Bridge TS Strike Key Loaded TACLANE INE Strike LAN MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  24. SIPRNET Sneaker-Net Solution 4 TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF FRU TS Router TCIP TS Router SUBLAN MDS Router TCIP ISDS COMM TTWCS MDS ISDS MSN TCIP Bridge TS Strike Key Loaded TACLANE INE Strike LAN MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS S/W Encryption

  25. SIPRNET Solution 5 TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF FRU TS Router TCIP TS Router SUBLAN MDS Router TCIP ISDS COMM TTWCS ISDS MDS Sneaker-Net ISDS MSN Strike Router TCIP TS Strike Key Loaded TACLANE INE Strike LAN MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  26. SIPRNET Solution 6TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF TS Router FRU TS Router SUBLAN TCIP TCIP ISDS COMM MDS Router MDS TTWCS ISDS MSN Strike LAN Enclave Guard TCIP Bridge TS Strike Key Loaded TACLANE INE MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  27. SIPRNET Solution 7TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF TS Router FRU TS Router SUBLAN TCIP TCIP ISDS COMM MDS Router MDS TTWCS ISDS MSN TCIP Bridge Strike LAN TS Strike Key Loaded TACLANE INE Enclave Guard MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

  28. SIPRNET Solution 8TWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE Bridge NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF TS Router FRU TS Router SUBLAN TCIP TCIP ISDS COMM MDS Router MDS TTWCS ISDS MSN TCIP Bridge TS Strike Key Loaded TACLANE INE Strike LAN Enclave Guard MDS TCIP Secret Strike Key Loaded TACLANE INE S/W Encryption MDS TTWCS

  29. SIPRNET Solution 9bTWS End to End IP COMMS NCTAMS CMSA/APS/#FLT CircuitRouter Pier side Router TCIP MDS Router ADNS Policy Router BCA SUBMARINE NOC Fleet Router Policy Router CircuitRouter ISDS RF Secret ADNS Router What Type Keys? STT RF TS Router FRU TS Router SUBLAN TCIP TCIP ISDS ISDS COMM MDS Router MDS TTWCS Strike Router ISDS MSN TCIP TS Strike Key Loaded TACLANE INE Strike LAN Enclave Guard MDS TCIP Secret Strike Key Loaded TACLANE INE MDS TTWCS

More Related