Hardware Reference
In-Depth Information
Fig. 5. Process description example
For each process selected in the guide (see Section 5.1), the guide presents:
Its name
Most processes are named like their ISO/IEC 27001 equivalent, but little adjustments
were made to obtain more generic and global terms, which represents more clearly
their content.
Its description
In order to facilitate comprehension and enhance efficiency, the guide includes
awareness-raising elements all along its content. It explains for each process its moti-
vations, utility and consequences.
The detailed tasks
Processes are split across a simple set of tasks containing the sub-actions that should
be completed. They are first aggregated according to Codasystem's feedbacks for
readability and understanding, and will be improved after the next experiments.
Input/output documents and records
Linking the various steps to each other is complex. Thus, to facilitate organisation of
documents and “out of the box” deployment, each process directly refers to its inputs
and lists its own outputs. In this way, it is easier to mesh all the processes together and
facilitate templates production and use.
The people involved
As stated previously (Section 5.3), four categories of actors are defined. Those key
roles are assigned to each process when needed, giving immediate information re-
garding who should be involved and what are the hierarchical implications.
5.5 Experts Validation
ANSIL is the Luxembourg Information Society Standardisation Association. This
national association contributes to IT standardisation activities in Luxembourg, from
Search WWH ::




Custom Search