A newly installed Operating system is inherently insecure. It has a certain number of vulnerabilities, depending on such things such as the age of the O.S., the amount of services it provides, the existence of initial backdoors not already patched, and the use of default policies designed without security in mind
By Hardening Operating Systems we refer to the act of configuring an operating system with the aim of making it as secure as possible, so that we minimize the risk of getting it compromised. This usually implies applying patches, changing default O.S. policies, and removing (or disabling) non-essential aplications and/or services.
In this course we'll try to identify common O.S. vulnerabilities and how to defend the O.S. against them. Both UNIX (linux) and Windows type O.S. will be considered.
Contingency plan
1. Modifications to the contents
none
2. Methodologies
* Teaching methodologies that are modified
- Master session: videoconference
- Practices: supervised through ICT,
- Objective test and practical test: through Faitic, Moodle Teams or other UVigo and / or UDC tools.
3. Mechanisms of personalized attention to students
- Moodle: All teaching resources will be provided through Faitic.
- Teams or other video conferencing tools. Team sessions may be convened for tutoring
- Email: for any questions
4. Modifications in the evaluation
none
* Evaluation observations:
In the case of online teaching both the objective test and the practical test will be done using teams, faitic or remote campus
5. Modifications to the bibliography or webography
none
(*)The teaching guide is the document in which the URV publishes the information about all its courses. It is a public document and cannot be modified. Only in exceptional cases can it be revised by the competent agent or duly revised so that it is in line with current legislation.