Outcome 4 Flashcards

1
Q

Reasons for Implementing Physical Controls

A

Minimizes or removes the risk of:
- harm to people
- information being accessed inappropriately

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

Ways to Physically Secure the Building

A
  • CCTV
  • Motion Sensors
  • Physical Barriers to stop entry
  • Security passes to authorize access to secure areas
  • Biometric Authentication
  • Alarm systems
  • Security Guards
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Ways of Protecting Development

A
  • Version Control
  • User Authentication
  • Encryption
  • Software Updates
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Version Control

A

The practice of tracking and managing changes to source control.

Protects the integrity of the source code. Can also be used as a logging system - allows developers to check who added code to a solution

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

Single Factor Authentication

A

simplest method of authentication, just something you know
e.g. password

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

Two Factor Authentication

A

involves something you know, and something you have

e.g. a password AND an access token

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

Multi Factor Authentication

A

most complex form,
involves something you know, something you have, and something you are

e.g. a password, an access token and a biometric scan

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

Software Auditing

A

Designed to reduce the risks to software.

Not testing - instead looks at the quality of the software, not if it works etc

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

Software Auditing Examples

A
  • Testing the software for security compliance (pen testing)
  • Considering levels of user training required to operate the solution
  • seeing if internal documentation is adequate
  • identifying assets required to operate the solution
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Data Breaches

A

Happens when personal information is accessed or disclosed without authorization

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

Man in the Middle Attacks

A

Eavesdropping attack that could occur when a transmission takes place, that causes communications and data to be exposed to unauthorized third-parties.

Causes a communication to be transmitted through a third computer system (which an attacker controls), which then forwards the data to both sides of the conversation.

Often sensitive data is harvested, such as login information, or bank details

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

Man in the Middle Attacks - Ways to Protect

A
  • Reset all users passwords periodically
  • Use encryption (HTTPS/VPN’s)
  • Use 2FA
  • Look out for unusual activity
    • Such as a login from Russia
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Social Engineering

A

Relies on the manipulation of human nature to persuade the victim to provide personal information or to initiate a transaction.

Uses basic tricks of con artists, such as flattery and friendliness to gain trust.

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

Social Engineering

A
  • train users
  • keep anti-virus software up to date
  • Use spyware detection software
  • Do not open email or SMS attachments
  • refuse to give information over phone or by email
  • use 2FA
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

XSS

A

Cross Site Scripting

Occurs when an web application includes user-supplied data in a page sent to the browser without properly validating or escaping the content prior to acceptance from the server.

Allows malicious scripts to be interested into other peoples web browsers

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

SQL Injection

A

When user input causes the resulting SQL query to change from its intended action

17
Q

SQL Injection - can result in

A
  • data being maliciously modified, leaked, deleted or edited
18
Q

SQL Injection - to avoid

A
  • Don’t use dynamic SQL Queries
  • Prevent user supplied inputs from affecting the logic of the query
19
Q

Ways to Manage Risks Posed by Third Parties

A
  • Limit third parties access to data
  • Use a confidentiality agreement to reduce the risk of the third party sharing data
  • Only use third parties that are covered by Australian law - international third parties are not subject to aussie law
20
Q

Accidental Threats

A

Threats that are made as the result of poor training or poor design of UI

e.g. deleting important data because the solution didn’t show a warning box

21
Q

Event Based Threats

A

threats external to the organization and beyond the immediate control or influence of security planning to prevent

22
Q

Deliberate Threats

A

Threats that are made as the result of deliberate, malicious acts

23
Q

Main Characteristics of data Integrity

A

Correctness
Accuracy
Authenticity
Reasonableness
Relevance
Timeliness

acronym: CARART

24
Q

Characteristics of Data Integrity - Accuracy

A
  • Completeness - data is complete
  • Clarity - data that isn’t ambiguous
  • Consistency - data that is completely consistent
25
Q

Characteristics of Data Integrity - Authenticiity

A

Data can be confirmed to come from a verified origin

26
Q

Characteristics of Data Integrity - Reasonableness

A

checks if the data is plausible, makes logical sense, and satisfies common sense

27
Q

Characteristics of Data Integrity - Relevance

A

measures how closely a resource - such as a document, database or webpage corresponds to that persons desire for information

28
Q

Characteristics of Data Integrity - Timeliness

A

refers to the speed it takes for the data to be retrieved

29
Q

Examples of Ethical Issues in Software Development

A
  • Relationship between software developers and end users -> consider those who are put at risk as a result of the solution being built
  • Acknowledging work - especially open source code