Unified Capabilities Certification Office UCCO - PowerPoint PPT Presentation

1 / 27
About This Presentation
Title:

Unified Capabilities Certification Office UCCO

Description:

Conducts all interoperability certification testing. ... Focus of testing is to ensure Military Unique Features (MUF) such as Multilevel ... – PowerPoint PPT presentation

Number of Views:105
Avg rating:3.0/5.0
Slides: 28
Provided by: cru3
Category:

less

Transcript and Presenter's Notes

Title: Unified Capabilities Certification Office UCCO


1
Defense Information Systems Agency Department of
Defense
Unified Capabilities APL Testing Process
  • Unified Capabilities Certification Office (UCCO)
  • 10 Oct 2008
  • ucco_at_disa.mil

2
Agenda
  • Policy Documents
  • Unified Capabilities (UC) Approved Product List
    (APL) Process Overview
  • Unified Capabilities Certification Office (UCCO)
  • Information Assurance Testing
  • Interoperability Testing
  • Product Pre-submittal Responsibilities
  • UC APL Process Timeline
  • Questions

3
Guiding Policy Documents
  • CJCSI 6211.02C DISN CONNECTION POLICY,
  • RESPONSIBILITIES, AND PROCESSES
  • Establishes policy, responsibilities and
    connection approval
  • process requirements for subnetworks of the
    Defense
  • Information Systems Network (DISN).
  • CJCSI 6215.01C POLICY FOR DOD VOICE NETWORKS
    WITH REAL TIME SERVICES (RTS)
  • Directs DISA to manage the DSN/DRSN from end to
    end.
  • DoDI 8100.3 DoD Voice Networks
  • Directs Joint Interoperability and Information
    Assurance
  • testing of all components connected, or
    planned for
  • connection to the DSN, DRSN, or PSTN.
  • DoDD 8500.1 Information Assurance
  • Directs all information Technology to be IA
    tested and certified
  • before connection to the DISN.

4
Other Guidance Documents
  • Unified Capabilities Requirements (UCR 2007)
  • Specifies technical standards for
    telecommunication switching equipment to be
    connected to the DSN emphasis is on Military
    Unique Features, e.g., Multilevel Precedence and
    Preemption (MLPP).
  • DISA Security Technical Implementation Guides
    (STIG)
  • Defines technical security policies,
    requirements, and Implementation details for
    applying security to the DSN.
  • NIST Special Publication 800-42 (SP 800-42)
  • Guideline on Network Security Testing that
    describes multiple types of security tests used
    to assess vulnerabilities of telecom systems.

5
UC APL Product Certification Process
Interoperability Certification
Information Assurance Certification
IA Product Testing
JIC Product Testing
Both Certifications Required For PlacementOn
Approved Products List
DISN DAA Validation
Joint Staff Validation
UC APL
6
Unified Capabilities Certification Office
  • UCCO
  • Central point of contact for DSN connection
    approval and approved products list process and
    questions
  • http//www.disa.mil/dsn/ops_connect.html
  • Manages IO and IA test team schedule
  • Coordinates and tracks product status on testing
    schedule, test results, and the UC APL. 
  • Provides Sponsors/vendor tracking numbers to
    track product
  • Submits the proper certification documentation
    for the product to the DISN Security
    Accreditation Working Group (DSAWG)
  • Contacts the sponsor with the decision regarding
    their submittal.

7
UCCO Coordination Members

Sponsor
Vendor
IA Test Team
CIO
UCCO
ASD/NII
FSO
DoD Components
DSN SSM
DSAWG
8
Information Assurance Testing
  • Supported by test teams at
  • JITC, Ft Huachuca, AZ
  • Air Force Information Operations Center
    (AFIOC), San
  • Antonio, TX
  • Composed of two (2) phases
  • Phase I Security Technical Implementation Guide
    (STIG) compliance, Functional Security Tests
  • Phase II IP Penetration Testing and Telephony
    Testing
  • Validates product compliance with Federal and
    DoD IA
  • requirements
  • IA test results
  • Vendor mitigations evaluated by Field Security
    Office (DISA)
  • for certification recommendation by Certifying
    Authority to
  • DISN Security Accreditation Working Group

9
Interoperability Testing
  • Joint Interoperability Test Command (JITC)
  • Conducts all interoperability certification
    testing.
  • Cooperative Research and Development Agreement
    (CRADA) between JITC and vendor is used to
    exchange cost of test services for vendor
    equipment. Benefits both vendor and Government
  • Fee for service when CRADA not applicable
  • Ensures end-to-end interoperability of voice
    switching systems by validating all Telecom
    equipment connected to the DSN meets applicable
    Unified Capabilities Requirements (UCR)
  • Focus of testing is to ensure Military Unique
    Features (MUF) such as Multilevel Precedence and
    Preemption are met
  • Test outcome is JITC certification letter that is
    validated by Joint Staff

10
Product Pre-submittal Responsibility
11
Step 1 Submittal
  • STEP 1 Applicant Agrees to the following prior
    to submittal
  • Payment or CRADA.
  • Provide Technical Documentation prior to
    receiving tracking number from UCCO.
  • Apply all applicable STIGs requirements. Submit
    Self-assessment Results (SAR) and mitigations to
    UCCO no later than 2 weeks prior to scheduled
    test date.
  • Will provide on site engineering support during
    all phases of testing.
  • Agree to ship equipment to alternate test
    facility if UCCO assigns test there
  • STEP 2 Complete submittal form.
  • STEP 3 Download Test Requirements Bundle
  • STEP 4 UCCO verifies Non-DSCD. If not, the
    sponsor is changed to DSCD WG.
  • STEP 5 Notify all parties.

Applicant
Sponsor
Submits UC APL Test Request
UCCO Determines Non-DSCD Sponsor?
No
Yes
http//www.disa.mil/dsn/jic/index.html
12
Step 2 Vendor Pre-Scheduling Actions
Applicant
  • Complete STIG checklist.
  • Provide STIG checklist and Product Technical
    Documentation IAW requirements outlined in Rules
    Of Engagement (Test Requirements Bundle) to UCCO.

Sponsor
Vendor
UCCO
13
Step 3 UCCO Verification
  • UCCO
  • 1) Upon receipt of STIG Checklist and
    documentation DISA will verify technical
    sufficiency (clock starts).
  • 2) Send Sponsor Verification Email to solution
    sponsor requiring verification of the following
  • Sponsorship of submitted solution
  • Agreement to review and confirm solution
    deployment configuration provided by vendor
  • Agreement to attend scheduled Outbrief for
    solution
  • 3) Send CCB Notification Email
  • Contact UCCO if any issues
  • 4) Sponsor verifies all items in email to UCCO.

UCCO
Sponsor
14
Step 4 Tracking Number
UCCO
Sponsor
UCCO Assigns and distributes Tracking Number
after STIG Checklist and Product Documentation
received and Verification successfully completed.
15
Step 5 Scheduling
  • UCCO/Test Teams
  • TSSI Scheduling occurs every other Wednesday.
  • Schedule new products for IA/IO testing.
  • Make decisions on possible slips, postponements,
    and cancellations.
  • If cancellation occurs, identify potential
    replacement vendors (If Self-Assessment Report
    (SAR) requirement has been satisfied)
  • New schedule posted every other Friday
    http//jitc.fhu.disa.mil/tssi/schedule.html

16
Step 6 AO Initial Contact
  • STEP 1 Conducts Initial Contact Meeting (ICM)
    via teleconference with sponsor, vendor, IA, FSO
    and UCCO to discuss the following (Note
    Replaces Inbrief)
  • Submitted Product Documentation and Diagrams.
  • Describe the System Under Test (SUT)
    configuration
  • CRADA/Fee arrangements
  • FSO STIG Questionnaire and applicable STIGs
  • Scheduled IA test Dates
  • Tentatively schedule Outbrief date
  • Misc. Issues
  • STEP 2 Generates ICM minutes.
  • STEP 3 Minutes sent to sponsor for validation
  • STEP 4 UCCO/Test Teams/FSO supply
  • continuous support to
    vendor/sponsor.

Setup Discussion
Vendor
17
Step 7 Self-Assessment Evaluation
  • UCCO sends warning notification to vendor/sponsor
    1 week prior to Self-assessment due date.
  • Self-Assessment reports and mitigations due to
    UCCO NLT 2 weeks prior to scheduled IA test
    dates.
  • If Self Assessment is not received, the scheduled
    test window is cancelled.
  • Tracking Number is retired and vendor must
    re-submit when ready.

Vendor
Submits Self-Assessment
UCCO
18
Self-Assessment Criteria
  • Self Assessments must be received on time
  • Encourage early submissions to prevent last
    minute cancellations
  • Self Assessments must be complete
  • Requirements identified from STIG questionnaire
  • STIGs verified by IATT and FSO during ICM
  • Self Assessments must contain mitigations to all
    findings, particularly high risk

19
Step 8 IA Testing
  • Phase I STIG Testing
  • Phase II IP Penetration/Telephony Testing

IA Testing
  • Vendors will be required to provide on-site
    engineering support during all phases of testing.
  • Vendors will be allowed to fix findings/TDRs
    on-site within test window as long as doesnt
    interfere with completion of testing.
  • Note Not all phases are applicable to all
    solutions

20
Step 9 IA Testing Completed
  • IA Team Evaluates findings at end of each phase
    of testing with vendor
  • At end of testing, determination is made on
    whether or not to proceed to IO (UCCO in
    coordination with FSO, AO and IA Test Team)
  • Draft IA Findings letter is generated by IA Test
    Team NLT 1 week after completion of test.
  • Vendor completes mitigations and submits to IATT
    NLT 2 weeks after receipt of Draft IA Findings
    Letter.
  • All parties attend previously scheduled Out
    brief. (Approximately 3 weeks after completion of
    testing)
  • Final IA Findings letter is generated by IATT
    within 3 days after completion of Out brief

FSO
UCCO
Vendor
21
Step 10 IO Testing
IO Testing
  • Concurrent with IA Steps 11 - 12
  • IO testing process
  • Vendors will be required to provide on-site
    engineering support during all phases of testing.
  • Vendors will be allowed to fix findings/TDRs
    within test window as long as doesnt interfere
    with completion of testing.
  • Results of testing presented to Joint Staff for
    final approval.

Vendor Engineer
JIC Team
Solution
Results
Joint Staff
22
Step 11 Out brief (Parallel track)
1. Previously scheduled out brief occurs
approximately 3 weeks after completion of IA
testing. 2. Decision is made on the following
Option 1 Rework mitigations UCCO will make
official CA recommendation request upon receipt
of reworked mitigations. Option 2 Move
Forward IA Team Develops Security Assessment
Report (IA Findings Letter w/vendor mitigations
supplied) within 3 days. a) UCCO requests
official CA Recommendation letter. b) UCCO
creates DSAWG Read Ahead Briefing and requests
slot on agenda at next scheduled upcoming DSAWG.
Out brief Teleconference
Sponsor
23
Step 12 DSAWG(Parallel track)
  • DSAWG Board meets on a monthly basis
  • If successful, product will be approved for
    connection to DISN
  • If unsuccessful, product will be worked on a
    case-by-case basis

DSAWG
USD (I)
USD (ATL)
24
UC APL Process Timeline
Initial Submittal
4 mos
5 mos
6 mos
3 mos
2 mos
1 mo
APL Memorandum Released, product added to the APL
ICM
Note The above timeline assumes a 2 month
availability from new test request
  • Test Diagram
  • STIG Questionnaire
  • White papers, diagrams, manuals, etc

ICM Identifies what STIGs will be required for
the Self- Assessment
24
25
UCCO Points of Contact
  • Michael Washington
  • Hilario Moncada, Jr
  • DSN (312) 381-0462/0330
  • Comcl(703) 882-0462/0330
  • Steve Pursell
  • Patty Beaudet
  • DSN (312) 879-0154/3234
  • CML (520) 538-0154/3234
  • UCCO Group Email Alias UCCO_at_disa.mil

26
  • Questions?

27
www.disa.mil
Write a Comment
User Comments (0)
About PowerShow.com