Security, Intrusion/Malware/Exploit, SDLC Flashcards

(50 cards)

1
Q

Security = Safety?

A

Security =/= Safety

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Safety =

A

physische Sicherheit –> alerting if the situation becomes unsafe for humans and environment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Security =

A

process of ensuring safety and maintaining safeguards –> defending against humans with malicious or criminal intent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

IT Security =

A

Verteidgung von Computern gegen Intrusion und unauthorized use of resources.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Auf was baut Security auf?

A

Safety

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Security breaches may have … consequences

A

serious safety

Bspw. Steuerung von AKW etc.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Perimeter Security Devices

A

Firewall, App Gateways

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Hilft Perimeter Security Software-Bugs zu mitigieren?

A

Nein, hilft es nicht.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Defense in depth =

A
  • Zoning
  • Castle Approach
  • mehrere Schutzlayer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Is Perimiter security enough anymore?

A

No, therefore Zero-Trust

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are reasons that Perimeter Security is not enough anymore?

A
  • Moving to cloud
  • BYOD
  • Remote Work
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are generally the challenges regarding security:

A
  • Heterogeneous Environments have more work and less security
  • Virtualization concentrates risk
  • It’s impossible to protect what you don’t know
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Zero-Trust Grundsatz:

A

never trust, always verify

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Was passiert bei Zero-Trust?

A

Jeder Zugriff wird authentisiert.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Weshalb wurde Perimetersicherheit immer priorisiert?

A
  • Security war nicht der Fokus bei Programmierern
  • Security Professionals sind keine Softare Developers
  • Fokus von Softwareentwickler liegt auf Funktionalität
  • Kunde sind gewohnt fehlerhafte Software sowie Patches zu erhalten
  • Kunden können die Fehler in Software nicht kontrollieren –> focus auf Perimitersicherheit
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Intrusion =

A

unathorized act of bypassing security mechanisms of network or information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Intrustion - unauthorized access to:

A
  • Computer
  • Service
  • Data
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

To prevent intrusions, we have to avoid…

A

Vulnerabilites

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Vulnerability =

A

programming errors, which allow exploitation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Exploit =

A

technique to breach security of a network or information system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

0-Day exlpoit =

A

öffentliche unbekannter Exploit –> kein Security Patch

22
Q

Malware benutzt …

A

einen Exploit

23
Q

Payload =

A

Schädlicher Programmcode

24
Q

Malware =

A

Malicious Software

25
Ablauf von: - Exlpoit - Payload - Infection
26
Drive-By-Infection
27
3 Steps of an Attack
1. Infect target system 2. Exploit vulnerabilities (--> connect to C2) 3. Load malicious payload - steal information - erase data - encrypt hard drives (for ransom) - spread to other computers - erase itself to avoid detection
28
What systems contain errors?
Every system of minimum complexity --> Sicherheit so gut wie es geht erhöhen
29
Security...
- is not a programming problem only - must be considered from the very beginning on - is relevant in all phases of software development - cannot be fixed by using special methods or tools (no "quickfix") - cannot be seen isolated from deployment or operations
30
Growing code size and complexity -->
Feheranzahl steigt
31
Software Quality:
- Features of softwares necessary for meeting its requirements - Features of security and safety - those features are partly competing - importance of each feature depends on the project
32
Cost of Bugs -->
je früher erkannt, umso kostengünstiger
33
Wo werden die meisten Fehler gefunden?
34
Relationship: Development costs vs. maintenance costs -->
the earlier the cheaper
35
Source of Bugs Statistics
36
Cost of Bugs in relation to their source code
37
Bugs =
Programmflaws, Fehlfunktionen --> leading to incorrect or unexpected results and behavior
38
Ursprung von Bugs
- lack of communication - miscommunication or no communication - recurring ambiguity in requirements - missing process framework - programming errors - too much rework - self-imposed pressures - software complexity - changing requirements - egotistical or overconfident people - poorly documented code - obsolete automation scripts - lack of skilled tester
39
Software Life-Cycle activities
- Software specification (Requirement engineering) - Software design and implementation - Software verification and validation - Software evolution (software maintenance)
40
Process Models and RE
- Activities must be defined exactly and arranged along time scale - Process model is starting point for project planning and project management - process model must be adapted to the project and the development environment
41
Different (Top-Down) Models:
- Spiral - Prototyping - Waterfall
42
Software Engineering includes
- Construction - Control - Rollout - Operation and maintenance
43
Software Quality Assurance
- Functionality - Reliability - Usability - Efficiency - Maintainability - Portability
44
Wasserfall Model und Requirements Engineering
- Grosser Teil von Requirements Engineering ist am Anfang - Danach begleiten und Unterstützen
45
Eigenschaften von Wasserfall Model:
- strikt linear - Einfache Meilensteine - Relativ einfaches Project Management - Wenig Freiheit - nicht sehr flexibel
46
4 agile manifesto
- Individuals and interactions over Processes and tools - Working software over comprehensive documentation - Customer collaboration over contract negotiation - Responding to change over following a plan
47
Agile Prinzipien - kurz gesagt:
- Sachen nicht Doppelt machen - Keep it small and simple (KISS) - Collective code ownership - Functional and customer-oriented development
48
Scrum
- Sprints / Iteration = 2 week cycles - Daily scrum meetings - Product backlog - Product owner (defines the feature of the end product) - Scrum master (priorities the feature to be worked on in each sprint) - Team members - User
49
DevOps =
Development + Operations = kontinuierliche Entwicklung in Produktion
50
Impact von agiler Methode für Security Requirements Engineers
Stetiges Einbringen von Security Inputs. RE muss kontinuierliche durchgeführt werden.