H Annex Test 2

Front 1

Five core capabilities of Information Operations

Back 1

1. Military information support operations (MISO)

2. Military Deception

3. Operations security (OPSEC)

4. Electronic Warfare (EW)

5. Cyberspace Operations (CO)

Front 2

Offensive Cyberspace Operations

Back 2

1. Operations intended to project power by the application of force in and through cyberspace.

2. Collection of intelligence in cyberspace.

3. Cyber operational preparation of the environment.

4. Noticeable denial effects in cyberspace.

Front 3

Defensive Cyberspace Operations

Back 3

Operations passive and active, intended to preserve the ability to utilize friendly cyberspace capabilities and protect data, networks, and netcentric capabilities.

Front 4

Department of Defense Information Network Operations (DINO)

Back 4

Operations to build, design, configure, secure, operate, maintain and sustain DoD networks to create and preserve information assurance on the DoD information Network.

Front 5

The Four groups that IA policies can be categorized

Back 5

1. Senior IA management policy statement

2. Regulatory

3. Advisory

4. Informative

Front 6

The Five supporting elements of Information Assurance

Back 6

1. Availability

2. Authentication

3. Confidentiality

4. Non-repudiation

5. Integrity

Front 7

The four categories of Department of Defense (DoD) information systems

Back 7

1. Automated information systems applications

2. Enclaves (including networks)

3. Outsourced IT-based processes

4. Platform IT interconnections

Front 8

Federal Information Security Management Act (FISMA)

Back 8

The public law that requires each federal agency 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.

Front 9

CJCSM 6510.01

Back 9

The Department of Defense (DoD) level policy that defines the Defense-in-Depth information Assurance (IA) Architecture.

Front 10

DODI 8500.2 (Information Assurance Implementation)

Back 10

The DoD level policy that addresses the formulation of an Information Assurance (IA) Baseline.

Front 11

MCO 5239.2

Back 11

The Marine Corps Order (MCO) that establishes the Marine Corps Information Assurance Program (MCIAP)

Front 12

Marine Corps Enterprise Network (MCEN) Operational Directive

Back 12

1. Will assign network related actions that must be taken by recipient commands.

2. Frequently these messages will specify a deadline for accomplishing the directed actions.

Front 13

Marine Corps Enterprise Network (MCEN) Advisory

Back 13

Will disseminate valuable information or deliver recommendations for consideration by local commanders relative to network management, operations, security and defense.

Front 14

Designated Approving Authority

Back 14

1. Ensure that security is incorporated as an element of the information system life-cycle process.

2. Review the SAA to confirm that the residual risk is within acceptable limits.

3. The DAA accepts this responsibility and risk by issuing an accreditation statement.

4. The accreditation is based from the certification of the system.

Front 15

Information Assurance Manager

Back 15

1. Determines what security controls need to be in place to protect the information being processed.

2. Implements the overall IA program for the organization.

3. Multiple IAMs may exist within an organization.

4. Primary IA technical advisor to the DAA.

5. Ensure that system users are provided annual information assurance awareness training.

6. Develop and maintain a Command level IA program.

7. Ensure that all IAOs and Priveleged Users receive the necessary technical training and IA training, education, and certification to carry out their duties.

8. Notify the DAA when a system requires and accreditation or reaccreditation.

9. Conduct Risk Assessments of Marine Corps information systems in accordance with the methodology and tools approved by the MCEN DAA.

Front 16

Information Assurance Officer

Back 16

1. ISs are operated, maintained, and disposed.

2. All users have the requisite security clearances.

3. IT-users and operators read, understand and sign an appropriate Network User Agreement.

4. Software, hardware, and firmware comply with DAA approved security configurations.

5. The network, site, system, or application information system is certified and accredited.

6. Accreditation and/or certification support documentation is maintained.

7. Enforce security policies and safeguards.

Front 17

Certifying Authority

Back 17

Making technical judgement for system compliance IAW applicable DoD/DoN security requirements.

Front 18

The annual training requirement mandated for all Information Systems (IS) users

Back 18

Awareness and Refresher training - currently CYBERM0000 on MarineNet

Front 19

Event

Back 19

Any observable occurrence in a system and/or network.

Front 20

incident

Back 20

An adverse event in an information system and/or network or the threat of the occurrence of such an event.

Front 21

The Eight Categories of an Incident

Back 21

1. Malicious code

2. Unauthorized access

3. Inappropriate usage

4. Service disruption

5. Espionage

6. Hoaxes

7. Spillages

8. Multiple category

Front 22

The Six components of an Incident Response Policy

Back 22

1. Preparation

2. Detection

3. Containment

4. Eradication

5. Recovery

6. Follow-up

Front 23

Audit

Back 23

An independent review and examination of records and activities to assess the adequacy of system controls, to ensure compliance with established policies and operational procedures and to recommend necessary changes in controls, policies and procedures.

Front 24

How to conduct evidence processing

Back 24

1. Immediate action - when in doubt contact MCNOSC

a. Turn off/leave system on?

b. Seizure of equipment?

c. Technical evidence gathering

2. Policy or legal?

3. Notification

4. Documentation

a. Time

b. Date

c. Individual involved with action

d. Description of action

5. Chain of custody

Front 25

The purpose of the Department of Defense (DoD) Information Operations Condition (INFOCON) System

Back 25

1. Provides a framework within which the Commander USSTRATCOM, regional commanders, services chiefs, base, post, camp, station, vessel commanders or agency directors can increase the measurable readiness of their networks to match operational priorities.

2. Major chance is a shift from a threat focus to a readiness focus.

Front 26

The purpose of the Department of Defense (DoD) Information Assurance Vulnerability Management (IAVM) Program

Back 26

1. Provide management over mitigating vulnerabilities that are found in DoD information systems.

2. Identifying and correcting vulnerabilities.

Front 27

The three different functions of the DoD Information Assurance Vulnerability Management (IAVM) Program

Back 27

1. Information Assurance Vulnerability Alert - vulnerability is sever; compulsory.

2. Information Assurance Vulnerability Bulletin - vulnerability does not pose immediate risk.

3. Technical Advisory - vulnerability generally categorized as low risk.

Front 28

Step 1 of the IAVM

Back 28

DISA identifies vulnerabilities of significance to the DoD and reports them to the JTF-GNO.

Front 29

Step 2 of the IAVM

Back 29

The MCNOSC acknowledges receipt of IAVA and IAVB within five working days to JTF-GNO.

Front 30

Step 3 of the IAVM

Back 30

The MCNOSC will issue IAVM messages, which will be tailored to the specific information technology environment of the Marine Corps.

Front 31

Step 4 of the IAVM

Back 31

Configuration Control Authorities (Program Offices) issue approval to apply IAVM corrective action to Centrally Managed Systems.

Front 32

Step 5 of the IAVM

Back 32

Implementation of IAVM Message corrective Actions (via old Disk or Patch Mgmt)

Front 33

Step 6 of the IAVM

Back 33

Reporting of IAVM compliance is a third echelon reporting responsibility for Marine Corps Assets in NMCI AOR, non-NMCI managed assets and Deployed Networks.

Front 34

Step 7 of the IAVM

Back 34

Compliance Verification: the MCNOSC will validate MCEN compliance via vulnerability analysis tools and report these results to the Marine Corps DAA.

Front 35

Step 8 of the IAVM

Back 35

The MCNOSC will compile and submit an aggregated Service component report of IAVM compliance and extensions to JTF-GNO.

Front 36

The Elements of the Tactical Certification & Accreditation process workflow

Back 36

1. DIV Comm Company creates initial request.

2. DIV G-6 CAR endorses the package acknowledging the unit is authorized to exercise and draw services.

3. MEF G-6 IAM reviews package and the MEF CAR endorses the CAP to acknowledge they are authorized to connect and their package is complete.

4. Package is submitted to MCNOSC for review and forwarded to the MCEN DAA for approval questions.

Front 37

Certification & Accreditation enclosures and required documents

Back 37

1. Exercise request letter

2. Endorsement letters from each CAR starting with the MSC through the MEF

3. Information Systems Security Plan (ISSP)

4. IAM/IAO Appointment Letter

5. C4 Systems List

6. C4 Application List

7. Detailed Diagrams