| ... | ... | @@ -2,10 +2,6 @@ |
|
|
|
- [Introduction](#introduction)
|
|
|
|
- [Data file Directory Structure](#data-file-directory-structure)
|
|
|
|
- [Change Management Workflow](#change-management-workflow)
|
|
|
|
- [Knowledge, Skill, Ability, and Task Defined](#knowledge-skill-ability-and-task-definition)
|
|
|
|
- [KSAT Relationships in the MTTL](#ksat-relationships-in-the-mttl)
|
|
|
|
- [KSAT Proficiency Requirements](#ksat-proficiency-requirements)
|
|
|
|
- [Knowledge Skill Ability and Task files](#knowledge-skill-ability-and-task-json-files)
|
|
|
|
- [WORK-ROLE and SPECIALIZATIONS JSON files](#work-roles-and-specializations-json-files)
|
|
|
|
- [PROF (proficiency) JSON file](#prof-json-file)
|
|
|
|
- [Rel-Link JSON file](#rel-link-json-file)
|
| ... | ... | @@ -61,74 +57,6 @@ graph TD; |
|
|
|
IF_APPROVE-- Yes -->FINISH[Merged to Master]
|
|
|
|
```
|
|
|
|
|
|
|
|
## Knowledge Skill Ability and Task Definition
|
|
|
|
|
|
|
|
*The following are definitions for Knowledge, Skill, and Ability according to National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework (NCWF).*
|
|
|
|
|
|
|
|
**Knowledge** is a body of information applied directly to the performance of a function.
|
|
|
|
|
|
|
|
**Skill** is often defined as an observable competence to perform a learned psychomotor act.
|
|
|
|
Skills in the psychomotor domain describe the ability to physically manipulate a tool or
|
|
|
|
an instrument like a hand or a hammer. Skills needed for cybersecurity rely less on physical
|
|
|
|
manipulation of tools and instruments and more on applying tools, frameworks, processes.
|
|
|
|
|
|
|
|
A skill can be measured objectively via test. (e.g. Did they find a key, compile correctly, pass unit tests, etc.)
|
|
|
|
|
|
|
|
**Ability** is competence to perform an observable behavior or a behavior that results in an
|
|
|
|
observable product.
|
|
|
|
|
|
|
|
An ability requires a subjective determination to properly evaluate (e.g. OJT, Scenario, etc.)
|
|
|
|
|
|
|
|
*US Cyber Command's Cyberspace Standards Analyst Team (CSAT) defined a task as:*
|
|
|
|
|
|
|
|
**Task** A Succession of work activities used to produce a distinguishable and discernable output that can be independently used or consumed. Tasks should align to the roles and responsibilities associated with a work role, function, or position. Task statements should:
|
|
|
|
- Describe activities (not KSAs)
|
|
|
|
- Have a certain beginning and end
|
|
|
|
- Represent activities performed by an individual
|
|
|
|
- Stated as not too broad nor specific
|
|
|
|
- Have an identifiable output
|
|
|
|
|
|
|
|
## KSAT Relationships in the MTTL
|
|
|
|
|
|
|
|
Many, but not all, of our KSAs will be related to one another in a parent to child relationship. The Rel-Link JSON files (defined below) used for each KSA category (excluding Tasks) have a 'parent' key where this relationship is defined. Use the following guidelines when creating these relationships.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Item | Allowable Parent(s) |
|
|
|
|
| ------ | ------ |
|
|
|
|
| Knowledge | Skill, Ability, Task |
|
|
|
|
| Skill | Ability, Task |
|
|
|
|
| Ability | Task |
|
|
|
|
| Task | None |
|
|
|
|
|
|
|
|
## KSAT Proficiency Requirements
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The following are proficiency codes defined by the JCT&CS
|
|
|
|
|
|
|
|
| Knowledge Levels | Definition |
|
|
|
|
|-----|--------|
|
|
|
|
| A | An 'A' indicates the individual must be able to identify basic facts and terms about the subject.|
|
|
|
|
| B | A 'B' indicates the individual must be able to identify relationships of basic facts and state general principles about the subject.|
|
|
|
|
| C | A 'C' indicates the individual must be able to analyze facts and principles and draw conclusions about the subject.|
|
|
|
|
| D | A 'D' indicates the individual must be able to evaluate conditions and make proper decisions about the subject.|
|
|
|
|
|
|
|
|
| Skill/Ability Levels | Definition |
|
|
|
|
|-----|--------|
|
|
|
|
| 1 | A '1' indicates the individual must be familiar with this competency and be generally capable of independently handling simple tasks or assignments.|
|
|
|
|
| 2 | A '2' indicates the individual must be capable of independently handling some complex tasks or assignments related to this competency, but may need direction and guidance on others.|
|
|
|
|
| 3 | A '3' indicates the individual must be capable of independently handling a wide variety of complex and or high profile tasks or assignments related to this competency. Must be an authority in this area and or often sought out by others for advice or to teach/mentor others on highly complex or challenging tasks or assignments related to this competency.|
|
|
|
|
|
|
|
|
Each KSAT has a required proficiency defined for the associated work role. These proficiency codes are captured and mapped to each KSAT in the work role's TTL JSON files describe below. Furthermore, when creating training or evaluation content that satisfies one of more KSATs, there is an associated Rel-Link JSON File. Although several KSATs may be satisfied in the content related to this file, the proficiency code used should be for the core of the content.
|
|
|
|
|
|
|
|
For example, if an evaluation is created to develop a class that implements a singleton design pattern and singleton design has a KSA proficiency of 2, but the problem also addresses a KSA of creating functions which has a proficiency code of 3, the overall proficiency should be 2 to address the core topic of singleton.
|
|
|
|
|
|
|
|
## Knowledge Skill Ability and Task JSON Files
|
|
|
|
|
|
|
|
This section will describe the knowledge, skill, ability, and task JSON files. These files will contain every possible KSA&T for every work role/specialization in the organization. Each KSA&T will also contain KSA&T to KSA&T dependency information and general training and evaluation material information.
|
|
|
|
|
|
|
|
|
|
|
|
## WORK-ROLES and SPECIALIZATIONS JSON Files
|
|
|
|
|
|
|
|
This section will describe the WORK-ROLES.json and SPECIALIZATIONS.json files. These files currently house information about the evaluation and/or training repository URLs. The URLs will be used to populate the 'training' and 'eval' rel-link information during the 'insert-rel-link-artifacts.py' script. Mandatory field information below.
|
| ... | ... | |