Language of instruction : English |
Sequentiality
|
|
No sequentiality
|
| Degree programme | | Study hours | Credits | P1 SBU | P1 SP | 2nd Chance Exam1 | Tolerance2 | Final grade3 | |
| Master of Software Systems Engineering Technology | Compulsory | 135 | 5,0 | 135 | 5,0 | Yes | Yes | Numerical | |
|
| Learning outcomes |
- EC
| EC1 – The Master of Software Engineering Technology can communicate adequately, cooperate effectively, and take into account the economic, ethical, social and/or international context and (s)he is aware of the impact on the environment in all aspects of his/her professional thought-process and agency. (S)he displays an appropriate engineering attitude, including continuous attention to the development of his/her professional competencies --. [people, data literacy and essential software skills]. | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly. | | | - BC
| reflects in the report on the applicabilty of the approaches to apply systems thinking depending on the actual topic of the assignments. | | | - BC
| reflects in the report on what could/should be changed in the various assignments. | | - DC
| DC-M9 - can communicate in oral and in written (also graphical) form. | | | - BC
| writes a synthesized report on the findings for the various assignments. | | - DC
| DC-M11 - acts socially responsible and within an international framework. | | | - BC
| is aware of the ethical aspects of offensive and defensive security. | | - DC
| DC-M12 - shows a suitable engineering attitude. | | | - BC
| is capable of approaching a security problem creatively and independently. | | | - BC
| takes a different systems thinking viewpoint and mindset in approaching a system from an adversarial viewpoint. | - EC
| EC2 - The Master of Software Engineering Technology masters the necessary sets of knowledge and skills regarding the design of integrated, resilient software systems and can creatively conceive, plan and implement them as an integrated part of a series of methodologically ordered actions within multidisciplinary projects with a significant research and/or innovation component. [systems thinking] | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | - BC
| is able to take a systems thinker perspective regarding the system, its users and goals and the adversaries. | - EC
| EC3 - The Master of Software Engineering Technology has advanced knowledge and understanding of the principles and applications of software engineering, including software development processes, software architectures and the software life cycle, and can apply them, with an understanding of current technological developments, in complex and practice-oriented problem domains. [software engineering] | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | - BC
| is able to create an abstract representation of a software system to reason about its security and resilience. | - EC
| EC4 - The Master of Software Engineering Technology has advanced knowledge and understanding of principles and applications of contemporary wireless and mobile communication networks, and in this domain, (s)he can autonomously initiate, plan, critically analyse and solve problems in a well-founded manner with an eye for data acquisition and implementation, and with the help of simulation techniques or advanced tools. [connected] | | - DC
| DC-M1 - has knowledge of the basic concepts, structures and coherence.
| | | - BC
| knows the security and resilient characteristics of the different netwerk protocols. | - EC
| EC5 - The Master of Software Engineering Technology masters the necessary sets of specialised knowledge and skills for the design of modular, integrated software systems that, on the basis of data acquisition and data analysis, can make intelligent decisions and that are resilient (secure, robust and scalable), within multidisciplinary projects with an applied research and/or innovation component. [intelligent & resilient systems] | | - DC
| DC-M2 - has insight in the basic concepts and methods.
| | | - BC
| can explain in own wordings the basis concepts and techniques of secure and resilient systems and clarify examples. | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them.
| | | - BC
| can identify possible flaws in security and resilience and their causes. | | - DC
| DC-M6 - can select methods and make calculated choices to solve problems or design solutions.
| | | - BC
| can improve the security and resilience of a system. | | | - BC
| makes appropriate decisions regarding security and resilience during the design of a system. | | - DC
| DC-M7 - can use selected methods and tools to implement solutions and designs.
| | | - BC
| is able to use offensive and defensive tools and libraries. | - EC
| EC6 - The Master of Software Engineering Technology masters the necessary sets of specialised knowledge and skills regarding generic abstraction techniques such as virtualization and containerization in order to utilise the underlying hardware and software systems in a secure, protected, and efficient way. [virtual world] | | - DC
| DC-M2 - has insight in the basic concepts and methods.
| | | - BC
| is aware of the risks and possibilities for security and resilience when using virtualised technologies. |
|
| EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
|
Abstract: This course will provide an in-depth discussion of the resiliency and security practices employed in industry and academia. The topics will enable the students to understand the fundamentals along with the limitations of cyber security. An introduction to cyber security and resiliency ideas, trends, and the current state of affairs. We examine the issue from the standpoints of attackers, defenders, and societies.
Objective: From a technological, economic, legal (GDPR), and social perspective, students will explore the advancements, principles, issues, limitations, and key state-of-the-art practices in cyber security and resilience. Completion of the course will enable students to implement the best resiliency and security practices in interdisciplinary domains.
Examples of possible topics are:
- Defining resilience and security
- Secure Development Lifecycle (SDLC)
- Common software security flaws and weaknesses (e.g., buffer overflows, authentication flaws, broken access control, injection attacks, …)
- Common design principles, patterns, and tactics to build resilient and secure software (e.g., cryptography, authentication, access control, TLS protocol, OAuth, resilience patterns such as circuit breaker, …)
- Tools and techniques for analyzing the resilience and security of a design (e.g., threat modeling using STRIDE, SAST tools, fuzzing, simulations, …)
- Overview of existing knowledge resources and organizations (e.g., CVE, CWE, NIST SSDF, OWASP, …)
- Security of virtualized and containerized applications
- Link between security and privacy (GDPR, threat analysis using LINDDUN)
- Legal aspects and compliance (ethical hacking, laws and regulations regarding security and resilience)
|
|
|
|
|
|
|
Application Lecture ✔
|
|
|
|
|
|
Exercises ✔
|
|
|
Homework ✔
|
|
|
|
Period 1 Credits 5,00
Evaluation method | |
|
Written evaluaton during teaching periode | 33 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 12/20 |
|
|
|
|
|
|
|
|
|
|
Written exam | 67 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 10/20 |
|
|
|
|
|
|
|
|
|
|
|
Evaluation conditions (participation and/or pass) | ✔ |
|
Conditions | Students need to have at least 8/20 on either the evaluation during the academic year and the exam. |
|
|
|
Consequences | The total for the course will be at most 9/20. |
|
|
|
Second examination period
Evaluation second examination opportunity different from first examination opprt | |
|
|
 
|
Compulsory course material |
|
All slides and references will be distributed through the electronic learning platform. |
|
|
|
|
|
| Master of Teaching in Sciences and Technology - Engineering and Technology choice for subject didactics engineering & technology | Optional | 135 | 5,0 | 135 | 5,0 | Yes | Yes | Numerical | |
|
| Learning outcomes |
- EC
| ENG&TECH 2. The newly graduated student has advanced knowledge of and insight into the acquired specific subject didactics and is able to creatively conceive, plan and implement these in an educational context, in particular as an integrated part of a methodologically and project-based series of actions within a multidisciplinary STEM project with a significant component of research and/or innovation. | - EC
| ENG&TECH 3. The newly graduated student has advanced or specialised knowledge of and insight into the principles, structure and technologies of various industrial processes and techniques relevant to his/her specific subject didactics and can autonomously recognise, critically analyse and find methodical and well-founded solutions to complex, multidisciplinary, unfamiliar, practice-oriented design or optimisation problems with an eye to application, selection of materials, automation, safety, environment and sustainability, an awareness of practical limitations and attentiveness to current technological developments. |
|
| EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
|
Abstract: This course will provide an in-depth discussion of the resiliency and security practices employed in industry and academia. The topics will enable the students to understand the fundamentals along with the limitations of cyber security. An introduction to cyber security and resiliency ideas, trends, and the current state of affairs. We examine the issue from the standpoints of attackers, defenders, and societies.
Objective: From a technological, economic, legal (GDPR), and social perspective, students will explore the advancements, principles, issues, limitations, and key state-of-the-art practices in cyber security and resilience. Completion of the course will enable students to implement the best resiliency and security practices in interdisciplinary domains.
Examples of possible topics are:
- Defining resilience and security
- Secure Development Lifecycle (SDLC)
- Common software security flaws and weaknesses (e.g., buffer overflows, authentication flaws, broken access control, injection attacks, …)
- Common design principles, patterns, and tactics to build resilient and secure software (e.g., cryptography, authentication, access control, TLS protocol, OAuth, resilience patterns such as circuit breaker, …)
- Tools and techniques for analyzing the resilience and security of a design (e.g., threat modeling using STRIDE, SAST tools, fuzzing, simulations, …)
- Overview of existing knowledge resources and organizations (e.g., CVE, CWE, NIST SSDF, OWASP, …)
- Security of virtualized and containerized applications
- Link between security and privacy (GDPR, threat analysis using LINDDUN)
- Legal aspects and compliance (ethical hacking, laws and regulations regarding security and resilience)
|
|
|
|
|
|
|
Application Lecture ✔
|
|
|
|
|
|
Exercises ✔
|
|
|
Homework ✔
|
|
|
|
Period 1 Credits 5,00
Evaluation method | |
|
Written evaluaton during teaching periode | 55 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 12/20 |
|
|
|
|
|
|
|
|
|
|
Written exam | 45 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 10/20 |
|
|
|
|
|
|
Multiple-choice questions | ✔ |
|
|
|
|
|
|
Evaluation conditions (participation and/or pass) | ✔ |
|
Conditions | Students need to have at least 8/20 on either the evaluation during the academic year and the exam. |
|
|
|
Consequences | The total for the course will be at most 9/20. |
|
|
|
Second examination period
Evaluation second examination opportunity different from first examination opprt | |
|
|
 
|
Compulsory course material |
|
All slides and references will be distributed through the electronic learning platform. |
|
|
|
|
|
| Exchange Programme Engineering Technology | Optional | 135 | 5,0 | 135 | 5,0 | Yes | Yes | Numerical | |
|
|
|
Abstract: This course will provide an in-depth discussion of the resiliency and security practices employed in industry and academia. The topics will enable the students to understand the fundamentals along with the limitations of cyber security. An introduction to cyber security and resiliency ideas, trends, and the current state of affairs. We examine the issue from the standpoints of attackers, defenders, and societies.
Objective: From a technological, economic, legal (GDPR), and social perspective, students will explore the advancements, principles, issues, limitations, and key state-of-the-art practices in cyber security and resilience. Completion of the course will enable students to implement the best resiliency and security practices in interdisciplinary domains.
Examples of possible topics are:
- Defining resilience and security
- Secure Development Lifecycle (SDLC)
- Common software security flaws and weaknesses (e.g., buffer overflows, authentication flaws, broken access control, injection attacks, …)
- Common design principles, patterns, and tactics to build resilient and secure software (e.g., cryptography, authentication, access control, TLS protocol, OAuth, resilience patterns such as circuit breaker, …)
- Tools and techniques for analyzing the resilience and security of a design (e.g., threat modeling using STRIDE, SAST tools, fuzzing, simulations, …)
- Overview of existing knowledge resources and organizations (e.g., CVE, CWE, NIST SSDF, OWASP, …)
- Security of virtualized and containerized applications
- Link between security and privacy (GDPR, threat analysis using LINDDUN)
- Legal aspects and compliance (ethical hacking, laws and regulations regarding security and resilience)
|
|
|
|
|
|
|
Application Lecture ✔
|
|
|
|
|
|
Exercises ✔
|
|
|
Homework ✔
|
|
|
|
Period 1 Credits 5,00
Evaluation method | |
|
Written evaluaton during teaching periode | 55 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 12/20 |
|
|
|
|
|
|
|
|
|
|
Written exam | 45 % |
|
Transfer of partial marks within the academic year | ✔ |
|
Conditions transfer of partial marks within the academic year | 10/20 |
|
|
|
|
|
|
Multiple-choice questions | ✔ |
|
|
|
|
|
|
Evaluation conditions (participation and/or pass) | ✔ |
|
Conditions | Students need to have at least 8/20 on either the evaluation during the academic year and the exam. |
|
|
|
Consequences | The total for the course will be at most 9/20. |
|
|
|
Second examination period
Evaluation second examination opportunity different from first examination opprt | |
|
|
 
|
Compulsory course material |
|
All slides and references will be distributed through the electronic learning platform. |
|
|
|
|
|
1 Education, Examination and Legal Position Regulations art.12.2, section 2. |
2 Education, Examination and Legal Position Regulations art.16.9, section 2. |
3 Education, Examination and Legal Position Regulations art.15.1, section 3.
|
Legend |
SBU : course load | SP : ECTS | N : Dutch | E : English |
|