Common Body of Knowledge for Information Security and Critical Information and Communication...

1
Common Body of Knowledge for Information Common Body of Knowledge for Information Security and Security and Critical Information and Communication Critical Information and Communication Infrastructure Protection Infrastructure Protection Marianthi Theoharidou, Dimitris Gritzalis {mtheohar,dgrit}@aueb.gr Information Security and Critical Infrastructure Protection Research Group Dept. of Informatics, Athens University of Economics & Business (AUEB) Common Body of Knowledge Common Body of Knowledge Although definitions may vary, a Common Body of Knowledge (CBK) can be viewed as the conceptual means that defines the knowledge, which is considered essential for the cognitive background and the required skills of a professional. It serves as a tool to: characterize the contents of a knowledge field, provide an overview overview of a domain and at the same time a snapshot of its contents, clarify the boundaries boundaries of the field in regards of other disciplines, and can provide foundations for curriculum development curriculum development, training program/seminar design or professional certification and accreditation. Critical Information and Communication Infrastructure Critical Information and Communication Infrastructure Critical infrastructure Critical infrastructure is an infrastructure or asset the incapacitation, malfunction or destruction of which would have a debilitating impact on the health, security or social welfare of citizens (nationally or even internationally). Large complex Critical Infrastructures can not be viewed independently from Information and Communication Technology (ICT), as ICT supports CI's to become globally interconnected and evolve. It also makes them more complex and interdependent, more difficult to manage and control, and therefore more vulnerable. The growing dependence of national critical Infrastructures on the ICT infrastructure means that the former cannot be secure if the latter is not, and vice versa. Therefore the bonds between traditional Information Security and Critical Infrastructure Protection are strong and the boundaries between the two become even more vague, as Critical Infrastructures evolve. We view Information Security as the basis for Critical Information and Communication Infrastructure Protection and the latter as the new emerging paradigm. We approach CIP as (a) an Information Security or Information Assurance issue, (b) as an organizational issue, meaning that it involves also human factors, as well as (c) a legal and compliance issue, e.g. legal requirements, audit, fraud etc. Our goal goal is not to form a strict CIP CBK, as we think that the teaching of a course in CIP would be too specific for an undergraduate level of education. Such a course would fit more in the postgraduate level of education. This is why we think that CIP should be introduced to the students together with Information Security. This is a CBK that tries to link the two fields. We also believe that, to a large extent Information Security provides the foundations for Critical Information and Communication Infrastructure Protection. We view CIP with an emphasis on the underlying ICT. What we suggest is that the students begin their studies with foundations and major topics of Information Security and then progress towards more specific CIP issues. Teaching Sequence of the Domains Teaching Sequence Teaching Sequence We observe a number of associations between domains upon which the proposed teaching sequence is based. One type of relation is that one domain may contain topics which are sub-domains of another one, but the topics are analyzed in more detail. That means that a topic is introduced in a first domain but cannot be explained fully without the knowledge of a second, later domain, so the first domain contains a brief statement with a reference to further explanation in the second. Possible overlap between domains can only be limited and not totally avoided. When forming the teaching sequence we adopted two assumptions: (1) more generic topics should be addressed earlier than more specialized ones, following a general-to-detailed path, and (2) one domain that forms the basis for another one should be taught earlier. Based on the intra-connections identified above the following sequence was created. Marianthi Theoharidou, Dimitris Marianthi Theoharidou, Dimitris Gritzalis Gritzalis CBK for Information Security and Critical Information and Communication Infrastructure CBK for Information Security and Critical Information and Communication Infrastructure Protection Protection Athens University of Economic and Athens University of Economic and Business Business References References [1] Theoharidou M. , Xidara D., Gritzalis D., "A Common Body of Knowledge for Information Security and Critical Information and Communication Infrastructure Protection", International Journal of Critical Infrastructure Protection , Vol. 1, No. 1, pp. 81-96, 2008. [2] Theoharidou M. , Stougiannou E., Gritzalis D., "A Common Body of Knowledge for Information Security and Critical Infrastructure Protection", in Proc. of 5 th World Conference on Information Security Education (WISE-5), pp. 49-56, Springer, New York, June 2007. [3] Theoharidou M. , Gritzalis D., "A Common Body of Knowledge for Information Security", IEEE Security & Privacy, Vol. 4, No. 2, pp. 64-67, March/April 2007. Future Research Future Research Our future research plans include: Regular re-examination and update of the CBK. Restructure of the ISCIP CBK, in a way similar to those of the Computing Field reports by the ACM/IEEE Joint Task Force. This suggests to accompany it with course syllabus, teaching material, and recommended instruction hours. This would be a useful tool for designing ISCIP curricula oriented towards undergraduate or postgraduate academic education. Academic course development, or designing training programs for a specific topic or for ISCIP awareness programs . Development of a Security Laboratory Schema, which will further support (mainly but not only) the academic education on ISCIP. The ISCIP CBK Domains (2 nd Level of Analysis) Methodology Methodology Step 1: CBK Review We reviewed CBK from other disciplines or topics, such as Computing, Management, Software Quality, etc. in terms of structure, level of analysis, presentation tools, or teaching material. We then examined newer versions of CBK related to ISCIP, so as to see the same attributes as above, but also study the topics that they incorporate and the categorizations they choose. Step 2: ISCIP Curricula Review We reviewed thirty (30) relevant curricula , in terms of topics, industrial or academic orientation, and prerequisite knowledge. The review covered highly ranked US and European Universities, as well as universities which were referred to by academic publications for their security-related programs or innovations. Another determinant factor was the availability of online information on curricula and courses. All of the findings below provided insight upon the selection of domains the CBK should contain. Step 3: CBK Restructuring We used with the structure of the existing CBK as a basis. The CBK was thoroughly re-examined and compared to the additional terms/topics found by steps (2) and (3). Although the number of domains remained the same, some domains were merged, split, renamed, or new ones added. An in- depth analysis of each of these domains followed. The sources are the following: Online course structure and teaching material (lecture notes, presentations, etc.). Textbooks related to the topics of the domain. Academic publications on the topic of the domain or on relevant lab/courses design. The domains were developed following three cycles of reviewing and cross-checking with multiple references. When examining which topics to include, the first criterion was to add the most common terms that were repeated throughout most curricula or CBK. In order to refine some domains, we added elements by course descriptions, textbooks, or academic publications, which were not found in all curricula, but contributed to the analysis. CBK Scope Orientatio n Prerequis ites & teaching sequence Maximum level of analysi s Additio nal materia l (ISC) 2 CBK Informatio n Systems Security Industrial Business 2 nd CBK in “Rep. on Inf. Assurance Curriculu m Dev.” Informatio n Assurance Academic - 3 rd - NIST (800-16) Computer Security Government al Industrial Technical - 2 nd ASIS Business and Organizati onal Security Academic Industrial Business - 2 nd Inf. Sec. in Network Technolog ies CBK Network Security Academic - 2 nd - CPP CBK Security Management Industrial Business 2 nd AUEB CBK ISCIP Academic 3 rd Comparison to other ISCIP CBK Comparison to ISCIP-related CBK Comparison to ISCIP-related CBK Terminology and Orientation Terminology and Orientation There are lots of semantic dissimilarities, as the CBK choose variant terminology or group topics differently. The ASIS and CPP CBK do not cover Domains 3-7, as they have a clear business scope, so they do not focus on the technical countermeasures of ISCIP. One can also observe the technical orientation of the NIST CBK, as it is included in a Computer Security standard. The CBK which is more complete is the one developed by (ISC) 2 . Its orientation is closer to ours, which is apparent from the relatively similar grouping of domains and topics covered. Content Content Some include security models and architecture elements; some others include basic terminology. Almost all include Legal issues, but the same emphasis is not placed on ethics or social issues. With the exception of the two business CBK, Cryptography and Database Security are included in some of them. The domain of Access Control and Authentication is included in all of these, but not fully. The Network, Web and Communications Security issues are addressed in most CBK, but the naming varies, as well as the topics studied. Forensics is not studied as a separate domain; it is usually studied as crime prevention and investigation, or as audit. The two business-oriented CBK (suggested by ASIS and by CPP) place mainly their emphasis on Information System Security Management and Physical Security. The domain of Information System Security Management is a wide one, covering topics from Personnel Security to Risk Management. However, none of the existing CBK covers all the topics included in our CBK. Forensics and Cryptography are also analyzed and covered with more detail in the (ISC) 2 CBK. Critical Infrastructure Protection Critical Infrastructure Protection None are CIP-focused CBK, but rather Information Security oriented. Also, they were created earlier, when the topic was still immature. One cannot find the term Critical Infrastructure included in any of them, nor topics like infrastructure categories or threat and vulnerability analysis per sector. Critical Infrastructure Protection is dealt with, solely on top of Physical/Environmental Security, Business Continuity, Disaster Recovery, Forensics, Incident Response or Terrorism. However, these CBK view the topic in terms of protecting an Information System or an Organization and not under the prism and specific characteristics of a Critical Infrastructure or of a Critical Sector. Thus, the topics drawn upon Information Security are not re-examined and presented modified for this context. 1. Critical Infrastructures 1. Critical Infrastructures Categories/Sectors Infrastructure Inter-dependency Sector Similarities & Differences Asset Valuation International aspects 2. Threats and Impacts 2. Threats and Impacts (see Domain 9) Risk Factors Threats Vulnerabilities Impacts 3. Procedures 3. Procedures (see Domain 9) Risk Analysis Security Policy Security Certification Best Practices & Standards Control of Infrastructures Training & Awareness Programs Personnel Security 4. Human Factor 4. Human Factor (see Domain 2) Ethics Decision Making Insider Threat Personnel in Critical Functions 5. Physical and Environmental Security 5. Physical and Environmental Security Perimeter Security & Physical Access Control Safety in the Workplace Equipment Security Cabling security Theft Workstation Security Device and Media Control (e.g. Disposal, Reuse, Accountability, Backup, etc.) Fire Protection, Prevention & Detection Power Failure (e.g. UPS, Power Generators, etc.) Anti-Flood control (e.g. Sensors, etc.) Explosive/Chemical Detection & Mitigation 6. National and International Programmes 6. National and International Programmes for CIP for CIP 7. Legal Issues 7. Legal Issues (see Domain 2) Public Safety Legislation Data Protection Legislation 8. Forensics 8. Forensics (see Domain 8) Accident/Incident Investigation Private Investigation 9. Standardization and Professional 9. Standardization and Professional Certification for Certification for CIP CIP (see Domain 9) Domain 10: Physical Domain 10: Physical Security & CIP Security & CIP (3 nd Level of Analysis) 1. 1. Ciphers Ciphers Block Ciphers Stream Ciphers Performance Cipher Cryptanalysis 2. Symmetric Cryptography 2. Symmetric Cryptography Block Symmetric Cryptography Stream Symmetric Cryptography 3. Public Key 3. Public Key Cryptography Cryptography Algorithms 4. 4. Quantum Cryptography Quantum Cryptography Quantum Information, qbit Quantum Ciphering Quantum Cryptanalysis Attacks 5. Hash Functions 5. Hash Functions Attributes Use Types Algorithms Attacks 6. Authentication 6. Authentication (see Domain 5) 7. Digital Signatures 7. Digital Signatures Characteristics Examples of Digital Signature Schemes Signatures with additional functionality 8. Key Exchange and Management 8. Key Exchange and Management Key Exchange Techniques Key Life Cycle Issues Key Protocols Advanced Trusted Third Party Services 9. Digital Certificates 9. Digital Certificates Characteristics Roles Certification Process Types 10. Public Key Infrastructure (PKI) 10. Public Key Infrastructure (PKI) Certification Service Providers Certification Services 11. Attacks and 11. Attacks and Cryptanalysis Cryptanalysis Cryptanalysis Attacks on Cryptosystems 12. Patents and Standards 12. Patents and Standards (see Domain 2) Patents Standards 13. Legal 13. Legal Framework Framework (see Domain 2) Domain 3: Cryptography Domain 3: Cryptography (3 nd Level of Analysis) ΟΙΚΟΝΟΜΙΚΟ ΠΑΝΕΠΙΣΤΗΜΙΟ ΑΘΗΝΩΝ ΟΙΚΟΝΟΜΙΚΟ ΠΑΝΕΠΙΣΤΗΜΙΟ ΑΘΗΝΩΝ ATHENS UNINERSITY OF ECONOMIC AND BUSINESS ATHENS UNINERSITY OF ECONOMIC AND BUSINESS T T MHMA MHMA Π Π ΛΗΡΟΦΟΡΙΚΗΣ ΛΗΡΟΦΟΡΙΚΗΣ AccessControl and Authentication AccessControl and Authentication AccessControl Basic AccessControl M echanism s AccessControl M odels AccessControl Policies Intrusions M ulti-Level AccessControl AccessControl Languages Authentication Basics Protocols Authentication Data (3) Authentication System s Netw ork, W eb and Com m unications Netw ork, W eb and Com m unications Security Security Netw orkSecurity Protocols Cryptography (3) W irelessNetw orkSecurity Distributed System s Secure Netw ork Devices Attacks, Intrusionsand M alw are (4) IDS and M aliciousSoftw are Protection (4) Security Netw ork Technologies(2) SpecificNetw ork System s Netw ork Forensics(8) Legal Issues(2) Database Security Database Security Requirements(3) Secure Architecture and AccessControl forDatabases(5) Developing a Database Security Plan Related Security Issues(4, 6) Threats, Vulnerabilitiesand Counterm easures Advanced Issues Database Forensics(8) Ethical Issues(2) Legal Issues(2) Forensics Forensics Steps Data Collection (4, 6) Netw ork& W eb Forensics(6) Database Forensics(7) Hardw are Forensics Data Usage Prerequisites(2) Psychology (2) Inform ation System sSecurity Inform ation System sSecurity M anagem ent M anagem ent Risk Analysisand M anagem ent Security Policy M anagem entIssues(3, 4, 5, 6) Organizational Issues Physical Security and Critical Infrastructure (10) Com pliance (2) Audit(8) Productand System Security: Assurance and Evaluation Standardization and Professional Certification Physical Security and Critical Physical Security and Critical Infrastructure Protection Infrastructure Protection Critical Infrastructures Threatsand Im pacts(9) Procedures(9) Hum an Factor(2) Physical and Environm ental Security National and International CIP Program s Legal Issues(2) Forensics(8) Standardization and Professional Certification forCIP (9) Prerequisite Know ledge, BasicTerm s Prerequisite Know ledge, BasicTerm s and Security M odels and Security M odels Prerequisite Know ledge Security Term s Security M odels Ethical, Social, Psychological and Ethical, Social, Psychological and Legal Issues Legal Issues Privacy Copyright Ethics Training and Aw areness Social Engineering Com puterCrime Legal Issues Psychology Cryptography Cryptography Ciphers Sym metricCryptography PublicKey Cryptography Q uantum Cryptography Hash Functions Authentication (5) Digital Signatures Key Exchange and M anagem ent Digital Certificates PublicKey Infrastructure (PKI) Attacksand Cryptanalysis Patentsand Standards(2) Legal Fram ew ork (2) Softw are Security Softw are Security Secure Life Cycle (3) Softw are Vulnerabilities M aliciousSoftw are Operating System sSecurity (1, 8) Database Security (7) Law sand Legislation (2) 1 2 3 4 5 6 7 8 9 10 Note : (*) = references to other domains.

Transcript of Common Body of Knowledge for Information Security and Critical Information and Communication...

Page 1: Common Body of Knowledge for Information Security and Critical Information and Communication Infrastructure Protection Marianthi Theoharidou, Dimitris.

Common Body of Knowledge for Information Security and Common Body of Knowledge for Information Security and Critical Information and Communication Infrastructure ProtectionCritical Information and Communication Infrastructure Protection

Marianthi Theoharidou, Dimitris Gritzalis {mtheohar,dgrit}@aueb.gr

Information Security and Critical Infrastructure Protection Research GroupDept. of Informatics, Athens University of Economics & Business (AUEB)

Common Body of KnowledgeCommon Body of KnowledgeAlthough definitions may vary, a Common Body of Knowledge (CBK) can be viewed as the conceptual means that defines the knowledge,

which is considered essential for the cognitive background and the required skills of a professional.

It serves as a tool to:

characterize the contents of a knowledge field,

provide an overviewoverview of a domain and at the same time a snapshot of its contents,

clarify the boundariesboundaries of the field in regards of other disciplines, and

can provide foundations for curriculum developmentcurriculum development, training program/seminar design or professional certification and accreditation.

Critical Information and Communication InfrastructureCritical Information and Communication Infrastructure

Critical infrastructureCritical infrastructure is an infrastructure or asset the incapacitation, malfunction or destruction of which would have a debilitating impact on the

health, security or social welfare of citizens (nationally or even internationally). Large complex Critical Infrastructures can not be viewed

independently from Information and Communication Technology (ICT), as ICT supports CI's to become globally interconnected and evolve. It also

makes them more complex and interdependent, more difficult to manage and control, and therefore more vulnerable. The growing dependence

of national critical Infrastructures on the ICT infrastructure means that the former cannot be secure if the latter is not, and vice versa. Therefore

the bonds between traditional Information Security and Critical Infrastructure Protection are strong and the boundaries between the two

become even more vague, as Critical Infrastructures evolve. We view Information Security as the basis for Critical Information and

Communication Infrastructure Protection and the latter as the new emerging paradigm. We approach CIP as (a) an Information Security or

Information Assurance issue, (b) as an organizational issue, meaning that it involves also human factors, as well as (c) a legal and compliance

issue, e.g. legal requirements, audit, fraud etc.

Our goalgoal is not to form a strict CIP CBK, as we think that the teaching of a course in CIP would be too specific for an undergraduate level of

education. Such a course would fit more in the postgraduate level of education. This is why we think that CIP should be introduced to the

students together with Information Security. This is a CBK that tries to link the two fields. We also believe that, to a large extent Information

Security provides the foundations for Critical Information and Communication Infrastructure Protection. We view CIP with an emphasis on the

underlying ICT. What we suggest is that the students begin their studies with foundations and major topics of Information Security and then

progress towards more specific CIP issues.

Teaching Sequence of the Domains

Teaching Sequence Teaching Sequence We observe a number of associations

between domains upon which the

proposed teaching sequence is based.

One type of relation is that one domain

may contain topics which are sub-

domains of another one, but the topics

are analyzed in more detail. That

means that a topic is introduced in a

first domain but cannot be explained

fully without the knowledge of a

second, later domain, so the first

domain contains a brief statement with

a reference to further explanation in

the second. Possible overlap between

domains can only be limited and not

totally avoided. When forming the

teaching sequence we adopted two

assumptions: (1) more generic topics

should be addressed earlier than more

specialized ones, following a general-

to-detailed path, and (2) one domain

that forms the basis for another one

should be taught earlier. Based on the

intra-connections identified above the

following sequence was created.

Marianthi Theoharidou, Dimitris GritzalisMarianthi Theoharidou, Dimitris GritzalisCBK for Information Security and Critical Information and Communication Infrastructure ProtectionCBK for Information Security and Critical Information and Communication Infrastructure ProtectionAthens University of Economic and Business Athens University of Economic and Business

ReferencesReferences[1] Theoharidou M., Xidara D., Gritzalis D., "A Common Body of Knowledge for Information Security and Critical Information and Communication Infrastructure

Protection", International Journal of Critical Infrastructure Protection, Vol. 1, No. 1, pp. 81-96, 2008.

[2] Theoharidou M., Stougiannou E., Gritzalis D., "A Common Body of Knowledge for Information Security and Critical Infrastructure Protection", in Proc. of 5th World

Conference on Information Security Education (WISE-5), pp. 49-56, Springer, New York, June 2007.

[3] Theoharidou M., Gritzalis D., "A Common Body of Knowledge for Information Security", IEEE Security & Privacy, Vol. 4, No. 2, pp. 64-67, March/April 2007.

Future ResearchFuture ResearchOur future research plans include:

Regular re-examination and update of the CBK.

Restructure of the ISCIP CBK, in a way similar to those of the Computing Field reports by the ACM/IEEE Joint Task Force. This suggests to

accompany it with course syllabus, teaching material, and recommended instruction hours. This would be a useful tool for designing ISCIP

curricula oriented towards undergraduate or postgraduate academic education.

Academic course development, or designing training programs for a specific topic or for ISCIP awareness programs.

Development of a Security Laboratory Schema, which will further support (mainly but not only) the academic education on ISCIP.

The ISCIP CBK Domains (2nd Level of Analysis)

MethodologyMethodologyStep 1: CBK Review

We reviewed CBK from other disciplines or topics, such as Computing, Management, Software Quality, etc. in terms of structure, level of

analysis, presentation tools, or teaching material. We then examined newer versions of CBK related to ISCIP, so as to see the same attributes as

above, but also study the topics that they incorporate and the categorizations they choose.

Step 2: ISCIP Curricula Review

We reviewed thirty (30) relevant curricula , in terms of topics, industrial or academic orientation, and prerequisite knowledge. The review

covered highly ranked US and European Universities, as well as universities which were referred to by academic publications for their security-

related programs or innovations. Another determinant factor was the availability of online information on curricula and courses. All of the

findings below provided insight upon the selection of domains the CBK should contain.

Step 3: CBK Restructuring

We used with the structure of the existing CBK as a basis. The CBK was thoroughly re-examined and compared to the additional terms/topics

found by steps (2) and (3). Although the number of domains remained the same, some domains were merged, split, renamed, or new ones

added. An in-depth analysis of each of these domains followed. The sources are the following:

• Online course structure and teaching material (lecture notes, presentations, etc.).

• Textbooks related to the topics of the domain.

• Academic publications on the topic of the domain or on relevant lab/courses design.

The domains were developed following three cycles of reviewing and cross-checking with multiple references. When examining which topics to

include, the first criterion was to add the most common terms that were repeated throughout most curricula or CBK. In order to refine some

domains, we added elements by course descriptions, textbooks, or academic publications, which were not found in all curricula, but

contributed to the analysis.

CBK Scope OrientationPrerequisites

& teaching sequence

Maximum level of analysis

Additional material

(ISC)2 CBKInformation

Systems Security

Industrial Business √ 2nd √

CBK in “Rep. on Inf.

Assurance Curriculum

Dev.”

Information Assurance Academic - 3rd -

NIST (800-16)

Computer Security

Governmental IndustrialTechnical

- 2nd √

ASISBusiness and

Organizational Security

AcademicIndustrialBusiness

- 2nd √

Inf. Sec. in Network

Technologies CBK

NetworkSecurity Academic - 2nd -

CPP CBK Security Management

IndustrialBusiness √ 2nd √

AUEB CBK ISCIP Academic √ 3rd

Comparison to other ISCIP CBK

Comparison to ISCIP-related CBKComparison to ISCIP-related CBK

Terminology and OrientationTerminology and Orientation

There are lots of semantic dissimilarities, as the CBK choose variant terminology or

group topics differently. The ASIS and CPP CBK do not cover Domains 3-7, as they have

a clear business scope, so they do not focus on the technical countermeasures of ISCIP.

One can also observe the technical orientation of the NIST CBK, as it is included in a

Computer Security standard. The CBK which is more complete is the one developed by

(ISC)2. Its orientation is closer to ours, which is apparent from the relatively similar

grouping of domains and topics covered.

ContentContent

Some include security models and architecture elements; some others include basic

terminology. Almost all include Legal issues, but the same emphasis is not placed on

ethics or social issues. With the exception of the two business CBK, Cryptography and

Database Security are included in some of them. The domain of Access Control and

Authentication is included in all of these, but not fully. The Network, Web and

Communications Security issues are addressed in most CBK, but the naming varies, as

well as the topics studied. Forensics is not studied as a separate domain; it is usually

studied as crime prevention and investigation, or as audit. The two business-oriented

CBK (suggested by ASIS and by CPP) place mainly their emphasis on Information

System Security Management and Physical Security. The domain of Information

System Security Management is a wide one, covering topics from Personnel Security to

Risk Management. However, none of the existing CBK covers all the topics included in

our CBK. Forensics and Cryptography are also analyzed and covered with more detail in

the (ISC)2 CBK.

Critical Infrastructure ProtectionCritical Infrastructure Protection

None are CIP-focused CBK, but rather Information

Security oriented. Also, they were created earlier, when

the topic was still immature. One cannot find the term

Critical Infrastructure included in any of them, nor topics

like infrastructure categories or threat and vulnerability

analysis per sector. Critical Infrastructure Protection is

dealt with, solely on top of Physical/Environmental

Security, Business Continuity, Disaster Recovery,

Forensics, Incident Response or Terrorism. However,

these CBK view the topic in terms of protecting an

Information System or an Organization and not under the

prism and specific characteristics of a Critical

Infrastructure or of a Critical Sector. Thus, the topics

drawn upon Information Security are not re-examined

and presented modified for this context.

1. Critical Infrastructures1. Critical InfrastructuresCategories/SectorsInfrastructure Inter-dependencySector Similarities & Differences Asset ValuationInternational aspects

2. Threats and Impacts2. Threats and Impacts (see Domain 9)Risk FactorsThreatsVulnerabilitiesImpacts

3. Procedures3. Procedures (see Domain 9)Risk AnalysisSecurity PolicySecurity CertificationBest Practices & Standards Control of InfrastructuresTraining & Awareness ProgramsPersonnel Security

4. Human Factor4. Human Factor (see Domain 2)Ethics Decision MakingInsider ThreatPersonnel in Critical Functions

5. Physical and Environmental Security5. Physical and Environmental SecurityPerimeter Security & Physical Access ControlSafety in the WorkplaceEquipment SecurityCabling securityTheftWorkstation SecurityDevice and Media Control (e.g. Disposal, Reuse,

Accountability, Backup, etc.)Fire Protection, Prevention & DetectionPower Failure (e.g. UPS, Power Generators, etc.)Anti-Flood control (e.g. Sensors, etc.)Explosive/Chemical Detection & Mitigation

6. National and International Programmes for CIP6. National and International Programmes for CIP7. Legal Issues7. Legal Issues (see Domain 2)

Public Safety Legislation Data Protection Legislation

8. Forensics8. Forensics (see Domain 8)Accident/Incident InvestigationPrivate Investigation

9. Standardization and Professional Certification for9. Standardization and Professional Certification for CIPCIP (see Domain 9)

Domain 10: Physical Security & CIPDomain 10: Physical Security & CIP(3nd Level of Analysis)

1. 1. CiphersCiphersBlock CiphersStream CiphersPerformanceCipher Cryptanalysis

2. Symmetric Cryptography2. Symmetric CryptographyBlock Symmetric Cryptography Stream Symmetric Cryptography

3. Public Key 3. Public Key Cryptography Cryptography Algorithms

4. 4. Quantum CryptographyQuantum CryptographyQuantum Information, qbitQuantum CipheringQuantum CryptanalysisAttacks

5. Hash Functions5. Hash FunctionsAttributesUseTypesAlgorithmsAttacks

6. Authentication6. Authentication (see Domain 5)7. Digital Signatures7. Digital Signatures

CharacteristicsExamples of Digital Signature SchemesSignatures with additional functionality

8. Key Exchange and Management8. Key Exchange and ManagementKey Exchange TechniquesKey Life Cycle IssuesKey ProtocolsAdvanced Trusted Third Party Services

9. Digital Certificates9. Digital CertificatesCharacteristicsRolesCertification ProcessTypes

10. Public Key Infrastructure (PKI)10. Public Key Infrastructure (PKI)Certification Service ProvidersCertification Services

11. Attacks and 11. Attacks and CryptanalysisCryptanalysisCryptanalysisAttacks on Cryptosystems

12. Patents and Standards 12. Patents and Standards (see Domain 2)PatentsStandards

13. Legal13. Legal FrameworkFramework (see Domain 2)

Domain 3: CryptographyDomain 3: Cryptography(3nd Level of Analysis)

ΟΙΚΟΝΟΜΙΚΟ ΠΑΝΕΠΙΣΤΗΜΙΟ ΑΘΗΝΩΝΟΙΚΟΝΟΜΙΚΟ ΠΑΝΕΠΙΣΤΗΜΙΟ ΑΘΗΝΩΝATHENS UNINERSITY OF ECONOMIC AND BUSINESSATHENS UNINERSITY OF ECONOMIC AND BUSINESS

TTMHMAMHMAΠΠΛΗΡΟΦΟΡΙΚΗΣΛΗΡΟΦΟΡΙΚΗΣ

Access Control and AuthenticationAccess Control and Authentication

Access ControlBasic

Access Control MechanismsAccess Control ModelsAccess Control Policies

IntrusionsMulti-Level Access ControlAccess Control Languages

AuthenticationBasics

ProtocolsAuthentication Data (3)Authentication Systems

Network, Web and Communications Network, Web and Communications SecuritySecurity

Network Security ProtocolsCryptography (3)

Wireless Network SecurityDistributed Systems

Secure Network Devices Attacks, Intrusions and Malware (4)

IDS and Malicious Software Protection (4)Security Network Technologies (2)

Specific Network SystemsNetwork Forensics (8)

Legal Issues (2)

Database SecurityDatabase Security

Requirements (3)Secure Architecture and Access Control

for Databases (5)Developing a Database Security Plan

Related Security Issues (4, 6)Threats, Vulnerabilities and

CountermeasuresAdvanced Issues

Database Forensics (8)Ethical Issues (2)Legal Issues (2)

ForensicsForensics

StepsData Collection (4, 6)

Network & Web Forensics (6)Database Forensics (7)

Hardware ForensicsData Usage Prerequisites (2)

Psychology (2)

Information Systems Security Information Systems Security ManagementManagement

Risk Analysis and ManagementSecurity Policy

Management Issues (3, 4, 5, 6)Organizational Issues

Physical Security and Critical Infrastructure (10)

Compliance (2)Audit (8)

Product and System Security: Assurance and Evaluation

Standardization and Professional Certification

Physical Security and Critical Physical Security and Critical Infrastructure ProtectionInfrastructure Protection

Critical InfrastructuresThreats and Impacts (9)

Procedures (9)Human Factor (2)

Physical and Environmental SecurityNational and International CIP

ProgramsLegal Issues (2)

Forensics (8)Standardization and Professional

Certification for CIP (9)

Prerequisite Knowledge, Basic TermsPrerequisite Knowledge, Basic Termsand Security Modelsand Security Models

Prerequisite Knowledge Security Terms

Security Models

Ethical, Social, Psychological and Ethical, Social, Psychological and Legal IssuesLegal Issues

Privacy Copyright

EthicsTraining and Awareness

Social EngineeringComputer Crime

Legal IssuesPsychology

CryptographyCryptography

CiphersSymmetric CryptographyPublic Key CryptographyQuantum Cryptography

Hash FunctionsAuthentication (5)Digital Signatures

Key Exchange and ManagementDigital Certificates

Public Key Infrastructure (PKI)Attacks and CryptanalysisPatents and Standards (2)

Legal Framework (2)

Software SecuritySoftware Security

Secure Life Cycle (3)Software Vulnerabilities

Malicious SoftwareOperating Systems Security (1, 8)

Database Security (7)Laws and Legislation (2)

Access Control and AuthenticationAccess Control and Authentication

Access ControlBasic

Access Control MechanismsAccess Control ModelsAccess Control Policies

IntrusionsMulti-Level Access ControlAccess Control Languages

AuthenticationBasics

ProtocolsAuthentication Data (3)Authentication Systems

Network, Web and Communications Network, Web and Communications SecuritySecurity

Network Security ProtocolsCryptography (3)

Wireless Network SecurityDistributed Systems

Secure Network Devices Attacks, Intrusions and Malware (4)

IDS and Malicious Software Protection (4)Security Network Technologies (2)

Specific Network SystemsNetwork Forensics (8)

Legal Issues (2)

Database SecurityDatabase Security

Requirements (3)Secure Architecture and Access Control

for Databases (5)Developing a Database Security Plan

Related Security Issues (4, 6)Threats, Vulnerabilities and

CountermeasuresAdvanced Issues

Database Forensics (8)Ethical Issues (2)Legal Issues (2)

ForensicsForensics

StepsData Collection (4, 6)

Network & Web Forensics (6)Database Forensics (7)

Hardware ForensicsData Usage Prerequisites (2)

Psychology (2)

Information Systems Security Information Systems Security ManagementManagement

Risk Analysis and ManagementSecurity Policy

Management Issues (3, 4, 5, 6)Organizational Issues

Physical Security and Critical Infrastructure (10)

Compliance (2)Audit (8)

Product and System Security: Assurance and Evaluation

Standardization and Professional Certification

Physical Security and Critical Physical Security and Critical Infrastructure ProtectionInfrastructure Protection

Critical InfrastructuresThreats and Impacts (9)

Procedures (9)Human Factor (2)

Physical and Environmental SecurityNational and International CIP

ProgramsLegal Issues (2)

Forensics (8)Standardization and Professional

Certification for CIP (9)

Prerequisite Knowledge, Basic TermsPrerequisite Knowledge, Basic Termsand Security Modelsand Security Models

Prerequisite Knowledge Security Terms

Security Models

Ethical, Social, Psychological and Ethical, Social, Psychological and Legal IssuesLegal Issues

Privacy Copyright

EthicsTraining and Awareness

Social EngineeringComputer Crime

Legal IssuesPsychology

CryptographyCryptography

CiphersSymmetric CryptographyPublic Key CryptographyQuantum Cryptography

Hash FunctionsAuthentication (5)Digital Signatures

Key Exchange and ManagementDigital Certificates

Public Key Infrastructure (PKI)Attacks and CryptanalysisPatents and Standards (2)

Legal Framework (2)

Software SecuritySoftware Security

Secure Life Cycle (3)Software Vulnerabilities

Malicious SoftwareOperating Systems Security (1, 8)

Database Security (7)Laws and Legislation (2)

1

2

3

4

5

6

7

8

9

10

Note: (*) = references to other domains.