mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-27 23:04:05 -06:00
vault backup: 2022-10-10 11:27:45
This commit is contained in:
parent
44fa137253
commit
2c602c058e
@ -4,6 +4,9 @@ aliases:
|
||||
tags:
|
||||
- comp210
|
||||
- lecture
|
||||
sr-due: 2022-10-13
|
||||
sr-interval: 3
|
||||
sr-ease: 250
|
||||
---
|
||||
|
||||
# need in all phases
|
||||
@ -16,19 +19,19 @@ tags:
|
||||
more costly to fix bug in development than in design
|
||||
- the later we fix it the more costly it is
|
||||
|
||||
from the start
|
||||
## from the start
|
||||
- hire right people
|
||||
- with hacking mindset
|
||||
- so they alwasys think about security
|
||||
- invite customers to training and seminars
|
||||
- testing could uncover security issues
|
||||
|
||||
questions during feasability
|
||||
## questions during feasability
|
||||
- 
|
||||
- what are the implications for users if assets are lost
|
||||
- some information is more high risk that other information
|
||||
|
||||
during design
|
||||
## during design
|
||||
- should be designed in iterative manner
|
||||
- threat modelling
|
||||
- 
|
||||
@ -61,7 +64,39 @@ responsing to threats
|
||||
- remove problem
|
||||
- fix problem
|
||||
|
||||
- design choice sto counter threats
|
||||
- 
|
||||
|
||||
## during development
|
||||
- techniques vary based on type of software
|
||||
- sytem
|
||||
- firmware
|
||||
- drive
|
||||
- programming software
|
||||
|
||||
- common vulnerabilities
|
||||
- 
|
||||
|
||||
example connection string
|
||||
- 
|
||||
- can provide extraneous parameters to fiind the right ones
|
||||
|
||||
example SQL injection
|
||||
- 
|
||||
|
||||
tips for vailidation and preventing overruns
|
||||
- 
|
||||
|
||||
|
||||
## during evolution
|
||||
- assign security evagelist
|
||||
- plan "security days"
|
||||
- learn from mistakes
|
||||
- minize attack surface
|
||||
|
||||
## stack overflow
|
||||
- 
|
||||
|
||||
|
||||
# summary
|
||||

|
||||
|
||||
33
content/notes/22-digital-preservation.md
Normal file
33
content/notes/22-digital-preservation.md
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "22-digital-preservation"
|
||||
aliases:
|
||||
tags:
|
||||
- comp210
|
||||
- lecture
|
||||
---
|
||||
|
||||
how long will data survive?
|
||||
|
||||
data rot
|
||||
- eveything wears out
|
||||
- digital media degrades
|
||||
- unreadable media
|
||||
- damaged files
|
||||
- backups may help
|
||||
- hardware and software becomes obsolete
|
||||
- cloud service shut down
|
||||
- os no longer exists
|
||||
- no device to read media
|
||||
- no software to read files
|
||||
- format documentation non-existent or missing
|
||||
- file system changes - lost metadata
|
||||
|
||||

|
||||
|
||||
Dark ages 2
|
||||

|
||||
|
||||
|
||||
## preservation of digital material
|
||||
- continuous format migration
|
||||
-
|
||||
@ -41,4 +41,5 @@ No final exam
|
||||
- [18-ML-in-IA-2](notes/18-ML-in-IA-2.md)
|
||||
- [19-deepfakes](notes/19-deepfakes.md)
|
||||
- [20-SE-in-IA](notes/20-SE-in-IA.md)
|
||||
- [21-SE-in-IA-2](notes/21-SE-in-IA-2.md)
|
||||
-
|
||||
Loading…
Reference in New Issue
Block a user