GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2025-12-24 13:24:05 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

vault backup: 2022-06-13 14:31:19

Browse Source
This commit is contained in:
Jet Hughes 2022-06-13 14:31:19 +12:00
parent ae0e5c31ca
commit 70eba8be27
3 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
content/notes/22-performance-and-security.md
View File

@ -144,6 +144,8 @@ Things to consider
- legilsations complliance
- needs to be integreated into application and database
- and considered throughout development
- least privilege
- a user should only have access to what they absolutely need in order to perform their responsibilities, and no more.
# Integity and securuty controls
- ensure correct system function by:
@ -170,6 +172,11 @@ increased security -> decreased accessiblility and usability
- ouput control (exfiltration prevention)
- system security
- user authentication and authorisation
- In authentication process, the identity of users are checked for providing the access to the system. While in authorization process, person’s or user’s authorities are checked for accessing the resources. Authentication is done before the authorization process, whereas authorization process is done after the authentication process.
- | Authentication determines whether the person is user or not. | While it determines What permission do user have? |
- authentication| Example : Employees in a company are required to authenticate through the network before accessing their company email.
- authorization | Example : After an employee successfully authenticates, the system determines what information the employees are allowed to access. |
- authentication methods
- security patches and updates
- preventing or mitigating known attack vectors

1
content/notes/review-i201.md
View File

@ -108,6 +108,7 @@ tags:
- consider throughout development
- authentication and authorisation
- principle of least privilege
- hat a user should only have access to what they absolutely need in order to perform their responsibilities, and no more.
# cost benefit analysis
- project feasbility [justifying a project](notes/25-cost-benefit-analysis.md#justifying%20a%20project)

3
content/notes/software-architectures.md
View File

@ -30,6 +30,9 @@ easy to deploy, awkward to upgrade.
- widely spaced "big bang releases"
usually only seen in legacy systems now
## service oriented architecture
https://www.ibm.com/cloud/learn/soa
## Separation of reponsibilities
partition systems into logically separated parts. e.g., UI, business rules, data access, utilities