Intro Flashcards
What can loss mean?
- financial loss both direct and indirect
- recovery cost
- productivity loss
- business disruption
- reputation damage
What can we say about the complexity of the ICT scenario?
Complexity is an enemy of obscurity. Related to this there is the first axiom of engineering: “The more complex a system is, the more difficult its correctness verification will be, meaning its implementation, management, operation”. Based on it there is the KISS concept: Keep It Simple, Stupid
How can we perform a risk estimation and which approaches can we have?
We have to take into account:
* service
* a service is implemented via an asset = set of good, data, Human Resources
* there are some event related to the asset:
* vulnerabilities: intrinsic weaknesses of that asset, including natural events
- threats: possibile deliberate action (Attack) or accidental event that can produce the loss of a security property by exploiting a vulnerability
- the consequences of these events are measured on their impact and their probability of happening
- from these measures we get to estimating the risk by listing all the possible risks prioritizing them by their impact and by the available time and budget
How to represent the risk estimation:
- risk assessment matrix
- risk heat map
Approaches:
1. address the most important risk
2. maximize the number of risks covered
Which are the basic problems in the ICT scenario insecurity?
- humans: they are not aware of the possibile risks, they have a natural instinct to trust, they don’t understand complex architectures…
- attackers use social techniques: they target users via mail, phone, …, they put psychological pressure on people or they study their their habits to make them lower their level of defense
- most networks are insecure: communication in clear, via broadcast, with shared links, using third party routers
- weak user authentication, often password based + no server authentication
- software with many bugs
What is a Zero Trust Architecture?
It is an architecture implemented above the concept “the enemy is everywhere”
Incident - data breach - data disclosure
Incident: a security event that compromises the integrity, confidentiality, availability of an asset (security properties)
Data breach: and incident that results in the disclosure or potential exposure of data
Data disclosure: a breach for which it was confirmed that data was actually disclosed and not just exposed to an unauthorized party
What is C.I.A. in the security field?
Confidentiality, integrity, availability (pyramid)
Which are the components of a cyber threat?
- Actors + Motivation
- actors = pyramid: people who do it just for fun-> criminal who do it for profit -> organized crime -> terrorists -> APTs (Advanced Persistent Threats, for example governments)
- motivation: MICE = Money, Ideology, Compromise, Ego
- Vulnerable target
- Vectors = Vulnerabilities + context
Which are the standardization Bodies for cybersecurity?
ISO, ITU… TODO
Which are the security principles? Just list them
- security in depth
- security by default
- neet-to-know
- least privilege
- security by design
Security in depth
It is one of the security principles.
It refers to the practice of using multiple layers of security controls (defensive mechanisms) throughout an information system. The idea is that if one layer fails, another will stop the threat, thereby providing a comprehensive defense strategy against a wide range of threats.
Example: An organization might implement a firewall to prevent unauthorized access from the internet, use encryption to protect data in transit, deploy antivirus software to detect and remove malware, and enforce strong authentication mechanisms. Even if a hacker bypasses the firewall, the encryption and antivirus layers provide additional barriers to protect the data.
Security by default
It is one of the security principles.
It means that the default configuration settings of software products and systems are set to the most secure settings possible. This principle ensures that without any additional configuration, the system will operate in a secure manner, minimizing the risk of vulnerabilities due to misconfiguration or default weak settings.
Example: When a person get a wifi modem from a company he is forced to change the password in order to use it
Need-to-Know
It is one of the security principles.
The need-to-know principle restricts aims to give access to information only to parties that require it to carry out their duties. This can lead to reduce the risk of unauthorized disclosure or access.
Example: consider a company that has various departments, each handling different types of sensitive data. Under the Need-to-Know principle, employees in the finance department would have access to financial records and reports, but not to the human resources files, unless their job explicitly requires access to both.
Least privilege
It is one of the security principles.
The principle of least privilege involves providing individuals or systems the minimum levels of access—or permissions—needed to perform their duties. This reduces the risk of accidental or deliberate misuse of permissions and limits the potential damage from incidents, in fact the more the permission the more the possible attacks.
Example: A system administrator may have access to all systems for maintenance purposes, but a regular employee is only given access to the network resources necessary for their job, such as email, specific databases, or certain applications, and nothing beyond that.
Security by Design
It is one of the security principles.
Security by Design means that security is integrated into IT systems from the earliest stages of development, rather than being added as an afterthought. This approach entails considering security in all aspects of system design and architecture, thereby ensuring that the system is fundamentally secure from the ground up.
Example: When developing a new software application, the development team incorporates input validation checks, secure authentication mechanisms, and encryption of sensitive data right from the planning and design phases, rather than retrofitting these security measures into an existing product.
When can we say that something is secure?
To say that something is secure means nothing, to say that something follows some of the security properties means a lot.
Which cases of data protection we have to consider in applying a security property?
- data in transit
- data at rest: in the device storage
- data at work: in RAM to be used
List all the security properties
- authentication: simple or mutual, peer or data
- authorization
- non-repudiation: formal proof, acceptable by a court of justice, that gives undeniable evidence of the data creator. It is not present when something is automatic
- privacy: of a communication, of data/action/position…
- integrity: this property leads to the detection of data modification, cancellation or filtering
- confidentiality: if data are changed this property doesn’t give the possibility to detect the changes ≠ integrity
- availability
- traceability, accountability
- serialization