itsa jennax @jennax-seceng - Tumblr Blog

Week 1 - The aftermath

Week 1 - Recon

The lecture

..felt more like a talk, covering a number of different concepts in various details.

Thread Modelling (watch this)

Fix low-hanging fruit first - delete unnecessary content and restrict access * HTTP Requests * DNS * Subdomains * Proxys * Enumerating Content - Active (Trying combinations) Passive (Watching your url) * Sniff testing - checking out how secure the website is

On proxys

This is something I didn't know.

Proxies exist to mark your identity to the server.

Proxies can load balance, cache data in order to save time. They can also allow bad people to intercept your requests.

Reverse proxies mean that the client doesn't know which server they're getting. This is useful for when a big domain has multiple servers and they are redirected anoniously to help load balance or test new services.

In getting started, we are required to set up a proxy. Honestly I just trusted the website and downloaded the proxy. The way it was done, was through email verification and then a password verification when installing the proxy.

So what we now have, is a certificate which recognises me, the user everytime I access quokkabank.com.

Then, we needed to sign in by changing the values within the site. Ahhhhh.

On Subdomains

Subdomains are created to organise and navigate different sections of a website.

Particular domains may not be accessible to the public.

A vulnerability may exist when a user finds a page they should not have access to.

This week's challenge involves Finding as many subdomains as you can.

To find subdomains you can use online pen-testing tools. Results.

dev.quokkabank.com

*.quokkobank.com

My dumb ass accidently closed the tab and this site only allows you to scan twice.

This is probably because they run thousands of words as tests to see if the subdomain exists - otherwise known as brute forcing.

It is also possible through manual searching in the terminal .

dig quokkabank.com

;; ANSWER SECTION: quokkabank.com. 195 IN A 184.168.221.57 ;; AUTHORITY SECTION: quokkabank.com. 3195 IN NS ns19.domaincontrol.com. quokkabank.com. 3195 IN NS ns20.domaincontrol.com.

dig @ns19.domaincontrol.com quokkabank.com axfr

;; communications error to 2603:5:21d0::a#53: end of file ;; communications error to 2603:5:21d0::a#53: end of file

Mine didn't work.. but supposedly AXFR (Authoritative transfer) which makes the client a "slave server" requesting data from a "master server."

Burp Suite

Hello 20T2, how’s Zoom?

Am going to reuse this blog for cs6443 Web Security. I enrolled in the course without fully checking what it is about... I just thought it would be fun. Anyhow, some things it covers:

Reconnaissance

Relevant Tooling Used in Industry

Server-side attacks, such as SQL injection and Local File Inclusion

Client-Side vulnerabilities, such as Cross Site Scripting

Authentication

Session Management

Access Control and Privilege Escalation

Common web service vulnerabilities

Patching and remediation

Secure web coding best practice

Vulnerability reporting and professional communication

Pen-testing in Industry

It seems to me that all the security courses have a rather unorthordox method of teaching, requiring much much more self learning and time management than any other course. It can be extremely harsh to those used to the baby-sitting of regular core courses, but at the same time, the more you invest, the more you get in return.

Requirements

CS6441 or CS3441 or CS9321

Basic Understanding of HTML, CSS, JS, DB, Server-Side Scripting etc

Moderate familiarity with Java, Python or PHP

Basic knowledge of network and web related protocols

Overall, I feel quite scared because, although I pass the requirements, week 1 seems like a huge slap to the face. No introduction, and even creating an account with Quakka bank leaves you racking ur brains.

I know I need this. So. Let's do it?

Clearing up my brain..

The puzzle as a whole

So far we've spend alot of time trying solving the age old puzzle of how to communicate while retaining:

Confidentiality

Integritiy

Availability

Clues to our puzzle

Confidentiality

Confidentiality means only the people who we want to read the message can read our message.

This can be ensured using:

Diffie Hellman Key-Exchange

Digital Signitures (RSA etc.)

AES

OTP and other encrpytion methods, but OTP being the strongest

Integrity

Integrity means that the content of the message must remain the same on both ends of the conversation.

This can be verified using

Hashing (e.g.MAC/HMAC, SHA-1, SHA-2)

AES

Combining our clues

Diffie Hellman Key Exchange

..is solely used for an initial key exchange, and is often extended upon by RSA.

Digital Signitures

..verify the sender of a message using public/private keys

Asymmetric

E.g. RSA, where a public and private key is based on the product of two large prime numbers

AES

..is a method of encrypting data using maths which I mentioned in my previous post

Symmetric

uses block ciphers (128bit, 192bit or 256bit)

Hashing

..is a method of quickly map a data on unknown size onto a piece of data of known size.

MAC (H(K| M) Hashing the key and the message)

Vulnerable to length extension attacks - But can be fixed with a salt

Even with a salt- OMG ITS 1AM ok continue dis tmr HAHA

PayID | Data Breach

Friday 16th August

> 90,000 Australian customers had their bank details exposed

3% of the total 3 million users

Information included:

Phone numbers

BSB Account numbers

Full name

Attacks happened before

~600,000 NPPA PayID looks up made from 7 compromised Westpac accounts

Brute forcing phone numbers in high density ranges of Australian phone numbers

Australian Security Consultant (Troy Hunt)

Allows Enumeration Attack (Brute-force to find valid users in the system)

AES (Adv. Encryption Standard)

You know the name, now you learn their story

Initially, (pre-1975) there were was no notion of a 'good crypto.'

NBS found its Lucifer and made the Data Encryption Standard (DES)

Modern Cryptography was born and the National Security Agency (NSA) was a proud father

DES had to be performed 3 times to fight off attacts and this became too inefficient

National Institute of Standards and Technology (NIST) looked for another a better crypto method

Rijndael won, defeating Serpent and Twofish (1997)

How it works

3 Key Concepts

Confusion: Obscure the relationship between the msg and the encrypted msg

Diffusion: Spread out the message (E.g. Column transposition)

Keys: Knowing the method, but only solving it with a key

Steps to encryption

Data is loaded into 4x4 squares (w/ Padding)

Data is XOR'd with the first round key (derived from the previous key)

How each round keys are derived

=> Take the last column of the previous key

=> Move top byte to the bottom

=> Perform substitution on the column

=> XOR the column with a round constant

=> XOR the result with the first column of the previous round key

=> Derive the rest of the column by XOR'ing the previous column with the corresponding column of the previous round key

=> Honestly, this is easier to understand if you read the comic

Perform substitution on the 4x4 box

Apply Diffusion (shifting rows to look like stairs and then wrapping them around to the other side)

XOR with the round key

Note: The bigger the key sides, the more rounds we perform.

Source:) The Stick Figure guid to AES by Moserware

no.. how does it really work (get ready for maths)

Homer Dudley

Specialised in Speech Science

Invented the Voderette (Could create a synthesized voice)

Invented Vocoder which replaced the A3 Scambler (US military)

A3 Scramble swapped high frequencies with low frequencies (no good!)

Vocoder broke down a human voice into basic components, compressed and transmitted these components via a shortwave channel to be recreated on the other side

Originally worked on it to improve telephone communication

Known as Project X

Sniffers would only hear buzzing sounds (Creating the nickname "the Green Hornet"

Source: Week 6 Activities Link to Podcast from 99PercentInvinsible

Weakness - Dishonesty

EDIT: This was really a rant. Gonna shorten this and cut to the chase xd

Intro

Our notion of honesty varies greatly depending on our environment and values as we mature and enter society. I tend to trust blindly - I've lost my wallet 4 times, phone 3 times, and left my bag outside in the sun to dry but nothing has gone wrong.

I trust that others to be honest, and hence, hold honesty as a important attribute.

White Lies

However, our consideration for another person may result in white lies. I believe we shouldn't overcomplicate our systems to take into account of worrying about another's concerns and leave that part to their own construct?

Lying to yourself

We often subconsciously alter a situation into one we like, believing things to fall into the same pattern as they always have, hence easily turning a blind eye to things to the small details which actually matter.

As a consequence of our predispositions, it is difficult to break the ideas and already identified patterns of behaviour/results.

Let's not form our own version of the truth so quickly and listen to each other. Our goal is not believe that things will go right because they always have but to check that things aren't going wrong.

trying to understand Richard..

Normal Accidents

This books preaches the failure of what we consider normal everyday accidents.

This book outlines the failures in which complex systems (not just softwares) in our everyday lives are poorly designed due to our shallow conception of safety and risk.

Perrow discusses the perils and of small accidents which snowball unpredictibly to create a large event with severe consequences.

The key problems with Perrow identifies have uncanny resemblence to what we have been taught to consider as bad code designed in O-O Design.

Complex System

Tightly Coupled

High Impact (Catatrophic Potential)

The Black Swan Theory

This theory is actuall extended from an old Latin expression. The latins believed that Black Swans did not exist until it was found later.

The black swan theory refers to unexpected events of large magnitude and consequences

Key idea; If you never expect something to happen, you don't prevent it and when it does happen and have a large impact, there are terrible consequences.

Chernobyl

Occured on 26th April 1986

Occured uring a safety test on the reactor

Test was a simulation of the electrical power outage to aid the development of a safety procedure for the cooling water circulation

People KNEW that it was a potential safety prolem which cause the nuclear reactor core to overheat

The test was delayed for about 10 hours

Supervisor didn't follow the procedure, creating unstable operating systems

Along with intentional disabling of reactor safety systems

Resulted in the nuclear chain reaction

Large amount of energy was suddeny released

Vapourised the cooling water

Caused a destructive steam explotion

Followed by a open-air reactor core fire which released radioactive contamination

So the question is, whose fault is it. One small mistake [TICK] Two small mistakes, three.. four... led to such a disaster.

...the catastrphic accident was caused by gross violations of operating rules and regulations...

DUN DUN DUN A N A L Y S I S

Problems:

The plant was not designed to safe

Did not have emergency protection systems capable of preventing the combination of events

Developers considered the combination of events to be impossible

the defiiencies in the reactor designs and operating regulations were set assigned and merely mentioned

Insufficient communiation between safety officer and the operators in chage of the experiment

Control was transferred from the process computer to human operators

Negligence during the contruction of the plant

The list goes on and on.. So the question remains - What can we do/take from this?

Design should be tested by multiple people from around the world (as each pair of eyes likes to focus on different things)

The construction must be overseen by people with different interests - not just contruction workers but also engineers who are able to focus on different problems which may potentially arise instead of construction workers just filling in the hole.

NEVER transfer process from computer to human, DISASTER PRONE!

Week 7B (Notes)

Assets (What are they?!)

When evaluating our problems, and defending against attackers, it is important to analyse and discuss our assets. They can be:

Tangible

Intangible

Monetary; etc

Strategies

No single person should be responsible for evaluation

Cetificates

Didn't really understand from the lecture, so this is my own research. If I have information wrong please do tell me! :)

What is SSL

SSL - Secure Sockets Layer

It is responsible for keeping the internet connection secure by safeguading sentitive data.

SSL Certificates

Browser/Server attempts to connect to a site secured with SSL

Server sends the browser/server a copy of its SSL certificate

Browser/server checks if it's trustworth

Server sends back a digitally signed acknowledgement to start a session

Encrypted data is shared between the browser/server and webserver

supersecure-blog

Week 6 Lectures

Never would I have thought that I would receive a lecture via a skype call… however this course continues to surprise me. Notes for this week’s lectures as per usual :) This week notes will be in their purest form: brain dribble.

Morning Lecture

WEP:

Needed a 64 bit key, but how do we get users to generate a 64 bit key. Was a lot to ask users to generate. Designers decided to generate the last 24 bits by themselves, using an IV.

Seed was different for each packet, 40 bit key that was shared and everyone used, and then the 24 bit value that was generated.

To decrypt, you get the 24 bit thing sent in the clear - (IV) and combine with the secret to get the 64 bit

Danger when someone transmits the same data under the same key - data is replicated in the same frame

Collision for IV - square root of 2^24 = 2^12 ~= 4000

Relatively small amount of packets needed to be sent before collision

Mixing data and control (key characteristic of attacks):

WEP attack - carrying out the normal function, can be abused by users to gain more control

I.e. Richard smuggling expensive express envelopes by hiding them in a satchel, posting them to himself

If there is a potential ambiguity in the channel and you are able to control how that is resolved - you gain control of the channel

Buffer Overflow:

Computer rapidly switches between jobs - “context switching” rather than concurrencyModern cpu’s use the notion of interruption Stack keeps track of what is being used

Latest process - top of the stack. When it’s finished, the information about the process gets thrown out, stack pointer gets moved down

After process have been re-awakened, need information about what the process is currently doing. This is stored in the disk, because RAM is expensive

Stack is also used to store local data about the program - much faster

Running program data is in the stack, as well as other frozen processes

Stack is stored backwards -> grows down

If can persuade the buffer you are writing to is bigger than it is - then you can be writing to other memory of the person that is asleep

Pointer to the next instruction about to be executed -> control

Contains other information

Write to the return address, overwrite the current thing

Proof of work:

Bitcoin - can’t counterfeit easily (work ratio)

No matter how good something is, every 18 months your attacker gains 1 bit of work due to Moore’s law i.e. lose one bit of security

Number of transistors per square inch on integrated circuits had doubled every year since the integrated circuit was invented.

Disk encryption:

Thread model - attacker has physical access to the disk, assume full control of the hard drive

Generate random key, encrypted version of the key stored in the disk

Evening Lecture:

Web Seminar

HTTP:

Application layer protocol used to send messages between browsers and web servers. HTTP requests go from the browser to the server.

Databases / SQL - browser sending an HTTP get request from the server with the username and password as data

Server queries database with “SELECT password FROM users WHERE match”

HTTP Cookies/Sessions

An HTTP cookie is a small piece of data sent in a response from a web server and stored on the user’s computer by the browser

A session cookies is a unique ID generated by the server and sent to the user when they first connect or login

Browser sends it with all HTTP requests

XSS - cross-site scripting is an attack in which an attacker injects data, such as a malicious program

Reflected XSS - occurs when user input is immediately returned by a web application.

Stored - you enter data which is stored within the application and then returned later

xss.game.appstop.com

SQL injection is a code injection technique in which malicious SQL statements are inserted into an entry field for execution.

Goal behind an SQL query is to gain access

‘ or 1 == 1 –

Blind SQL injections are identical to normal SQL Injection except that when an attacker attempts to exploit an application rather than getting a useful error message

Cross Site Request Forgery:

Attack on an authenticated user i,.e. Already logged in

When you log in to a website it sends you a cookie to your browser to keep you logged in.

Bank attack:

If attacker knows the format of the bank request, they can hide a transfer request inside an img using html

Cross Site Request Forgery Defences:

Primary mitigation is with tokens

Generate a suitably random token, store value server-side

Sent token to user, expect this token back as part of any user requests

In a GET request, this token will be appended to the URL

If a website has XSS vulnerabilities, CSRF mitigations are pointless

Crypto Seminar

Payment Process: Current versus Bitcoin:

Current payment systems require third-party intermediaries that often charge high processing fees

Machine-to-machine payment using the Bitcoin protocol allows for direct payment between individuals, as well as support micropayments -> reduce transaction costs

Crypto:

Built using cryptographic principles i.e. blockchain and hashing

Difficult to fake transactions - too many bits so it isn’t worth

Blockchain:

Method of storing data

A chain of chronologically linked blocks where each block is linked to the previous block

Blocks are unique - no two blocks will have the same hash

Data:

Consists of hundreds of transactions

Put around 2000 transactions in one block

Hashes:

Block’s hash summarises the data into a combination of letters and numbers

SHA-256 hashing algorithm

If a transaction in the block is changed, the hash is changed

This is important because each block has the hash of the previous block -> need to check against all previous blocks

Tamper evident

When a transaction is mine, it isn’t immediately added but placed in a transaction pool

The miner gathers enough to form a block - called a candidate block

Hash the block header along with a nonce

When we hash we hope the block hash value is below a certain target value

The nonce is a random number brute forced by miners to try and create the correct hash

When nonce is found, it is broadcast and the block is added to the existing chain

Proof of Stake:

Growth of mining pools could eventually lead back to a centralised system

PoW mining uses excessive amounts of electricity

PoS algorithm attributes mining power to proportion of total bitcoins held, rather than computing power

Rewards are transaction fees rather than new cryptocurrency

Types of crypto currencies:

Bitcoin

Uses the SHA-256 algorithm - very processor intensive and complex requires lots of dedicated hardware

Litecoin

More accessible for normal uses to mine on their CPUs as the algorithm used is less CPU intensive, but more memory intensive

Facebook Libra

Centralised architecture - libra will be managed by the Libra Association, having more control over the blockchain

There is no ‘mining” - to set up a node on Libra, need $10000

Privacy:

Blockchain doesn’t have a strong concept of identity (public, private) key pairing

Doesn’t exempt transaction from tracing

Two main ways:

Relations between address - inferring identity

Interactions between nodes and users

Monero:

Unlinkability -> stealth addresses with view keys

Transaction mixing -> ring signatures

Concealing transaction amounts -> RingCt signatures

Historical flaws:

51% attack:

Double-spend

Purpose might also be to discredit a crypto instead of money

Credibility decided on the majority

Off-springs created one’s solution for a hash is not added into their own spin-off

Motive might be to discredit the cryptocurrency

Past Attacks:

Usually happened on small networks

Verge 51% attack, on April 2018

Groups of hackers found two main flaws in the system:

Bug which lowered the hashing difficulty for a hashing algo (Scrypt)

Verge allowed 5 different hashing algorithms, and only the difficulty for Scrypt is lowered

Hacked 3 times over 2 weeks

Cryptocurrency exchanges:

Mt.Gox - bitcoin exchange that was launched in 2010. Handled over 70% of all Bitcoin transactions in 2013

Previous owner retained admin level user account when MtGox was sold in 2011

Attacker logged in to the account

Assigned himself a large number of BTC which he sold on the exchange

Price dropped immediately

Obtained private keys of MtGox clients

Created selling orders on these accounts and bought the BTC he stole

SQL Injection vulnerability was found

MtGox user database began circulating online and included:

Plain text email addresses

Usernames

MD5 Hashed passwords, with some unsalted

Future of Cryptocurrency:

Adoption

Overcoming resistance from:

People

Established finance institutes (eg banks)

Governments (they don’t like that you don’t pay tax by concurrency)

Ease of use

Volatility

Threats

Blockchain its laek

Quantum computers

To the sft that utilises cryptocurrency

Cryptocurrency wallet/exchange/

Strong private keys

Symmetric Ciphers

Two sorts of ciphers, symmetric and asymmetric -> regards the keys

If you know the key

For a symmetric: you can decrypt and encrypt

For an asymmetric: you have separate private and public keys to decrypt and encrypt (RSA)

Earthquakes:

How would I cope, how would my business cope? -> ‘gobag’

Home Study - read up about the “block modes” - only need to learn/understand ECB, CBC, CTR

Authentication:

Identifying for who? Computer/human?

Facebook. Police, baggage screening

Authentication and identification - what is the difference?

What decisions?

Computerised authentication system -> needs to make a decision about whether it is you or not

Factors:

Something that you have

Something that you know - i.e a password. Easy way of doing authentication

How do you know that you share the same secret?

Something that you are - Unfakeable

Two factor authentication:

Something that you have AND something that you know i.e. and password

All of these things seem different, but ultimately they are all just things that you know, and are all secrets

Something that you are can be replicated

Serious problem -> authenticating bombs, missiles etc

Biometrics - not real authentication, collecting another shared secret from a person, and can be bypassed

jennax-seceng

Sadly, I had missed this lecture and @supersecure had directed me to this blog which honestly saved my soul. Really like the way you make your dot points super succinct! Makes it easy to digest and quick to read :DD

halp it became wk8

Because of upcoming assessments, I am postponing all lecture and activity posts to wednesday next week. Things I need to catch on include:

Wk07 B (evening lecture)

Wk07 Case Study

Authentication Game

Block Cipher Modes

Threat modelling (!!!)

Security Everywhere - Logging into public wifi (admin)!! KEEN

Sth-Awesome Update 2

Overall Progress

I had a look at my goals for my project's progress plan and it turns out that I'm actually up to date (woah) as I am preparing the demos at the moment.

Progress from last week

It would appear that I haven't done much since the last two blogs... BUT I actually have been trying to setup a website so I can demonstrate the different vulnerabilities. For this, I did research on:

SQL Database

Flask (Using SQL and Flask together)

Javascript (Injection probabilities)

Bulma (everyone wants a pretty website right?)

EditThisCookie (Played around to see what I could do)

Yeeeeeeee.

Changes for the presentation

Previously, in my proposal I had several components. I had no idea that it was going to be covered within the course.. so I would like to adjust some of the components:

Explanation - what do they exploit

Less importance

Brief Explanation

Demo of exploitation

Instead of Altoro Mutrual, I will be doing it on my own website

Why does this occur, how we can fix/avoid it

This will be covered as we show improvements made to help the vulnerability in the demo

Extension: Find REAL websites which have such vulnerabilities

Extension: Find past examples of such exploitations

As a result, I would also like to make some minor adjustments to the marking criteria.

HD - 85-100 - ~~Very good~~ Explanation and Extensive and Well explained Demo of 3 vulnerabilities DN - 75-84 - ~~Very good~~ Explanation and Well explained Demo of 3 vulnerabilities CR - 65-74 - ~~Basic~~ Explanation and Good explanation Demo of 3 vulnerabilities PS - 50-64 - ~~Good~~ Good Explanation and Demo of 2 vulnerabilities

Week 07 (Notes A)

"Under Contruction"

Yay Richard is not sick anymore!!

Last Week | Duffie Hellman

I included this in my lecture notes for week 04 but apparently it wasn't properly covered and the notes are from my own research ?! (pat to myself).

AIM: To exchange a key without anyone being able to communicate privately

METHOD: Utilise exponentials as (a^b)^c = (a^c)^b

Covered in previous notes

Vulnerabilities

1) Memory Corruption | Buffer Overflow

Memory in C is dynamic, it uses stacks and heaps

This makes it easy to estimate where the memory address for a variable ends and write into the next piece of memory, changing the flow of code

Instead of writing some blah code myself and spending hours looking over the tutor's examples. I read (about 3 times) a fellow student's blogs. You can also find the entire thing here:

Part 1

Part 2

Part 3

Summary

In PART I, Alex declares two variables, team and name. As he explaines, this is stored in the memory looking something like

0x00000000 name (32 bytes) team (1 byte) 0xFFFFFFFF ------------------------------------------------------------- HEAP------->[ ][ ] <------STACK ^ Starts writing here

Because the memory is stored backwards, * name would be in address 0x000; and * team is stored in 0x033.

Hence, if we do: \x00' * 32 + 'B', it would overwrite into 0x033 which is the memory address of team!!

He also goes more in depth about how to actually do it in a 64bit architecture but ye.

In PART II, he builds onto to the example and demonstrates a more practical attack by overwriting the address that the function points to.

In the example code, gets is used once again!

But this time, we want to inject a memory position for the code to jump to - print("\x00"*64 + "\xd9\x61\x55\x56").

But how do we determine the memory address of this particular function?

Alex (the hackerman) has disabled ASLR (Addresss space layout randomization) using alias aslr='setarch $(uname -m) -R' pikachu :0

2) Memory Corruption | Integer Overflow

Integer overflow refers to when C interprets incredible big numbers as a negative

In C, the first bit for an integer represents the sign of the number

This can be exploited and be used to bypass error checking of lengths as seen below

Example

length = get_user_length(sockfc);

Here, length is not an unsigned integer. (Designated to be positive) This may be a problem as if an integer in C is too big, it becomes a negative number.

Hence, if an attacker creates a file of a very big length, it bypasses the following error checking code:

if (length > 1024) { // Do Something }

Now, the attack can redirect the buffer so that the code jumps into the attacker's malicious code

if (read(sockfd, buffer, length) < 0) { error(); return 1; }

3) Format String Attack

So, unsurprisingly, programmers are very lazy, and hence instead of doing printfs the proper way,

printf("%s\n", "Heeelllooo");

we short cut it and do something like:

printf("Heeelllooo here");.

This can be expoited (as all things are). For example, say we have the string:

string = "Heeeyyy %s"

and we tried to print this..

printf(string)

Well, it would print out the next piece of item.. Even, worse, an attacker could insert a string of code which WRITES TO THE MEMORY!!!

4) NOP Sleds

Very last thing, we learn about NOP Sheds, which is a way for finding a space for the malicious code to be injected.

NOP's are lines of code which do nothing.. and they actually occur very frequently in your code (yay mips). The trick to this one is to start off the the malicious code with lots of NOP's which act as a landing strip for the code.

Ok Lowkey didn't quite understand and will update in Notes B.

Case Study - Wk06

We're in war. Main internet threats?

Government Officials

Data Theft

DDoS

Transport Networks

Electricity

Communication

Military Information

Insider Attacks

10 Reccomendations for actions to be taken

Comparmentalise knowledge of intelligence

JUSTIFICATION - Reduce the impact of insider attacks

Government announcements should be anonymous

JUSTIFICATION - Military/Citizens may be bias against party/party members.

JUSTIFICATION - Decisions may be traced by enemies. By exposing who made what decision we expose our strengths AND our weaknesses. On the otherhand, if it is anonymous, then there's no single target and it is harder to know who to aim for.

Government officials should not be known to the public

JUSTIFICATION - Government Officials are a vulnerable target as can be held hostage when it comes to making plans for the country

Sensitive data is to be re-classified

JUSTIFICAION - Data which is kept relatively public within today's peaceful world may become very important and should be sensitive within a war-like situation.

Military Movement/Orders should be encrypted

JUSTIFICATION - We don't want the enemy knowing our actions (Like how we know China has docked their aircrafts on the shores of Taiwan xd)

Backdoor

JUSTIFICATION - Exploit our global connections to backdoor before they find out (0-Day)

Others

In the event of DDoS, have backup services which would continue running (Prevents SPF)

Background Checks on Engineers/Politians

International wargames for preparation and training

Wk6 Case Study - Preparation

Suppose we are thrust into a war with a superpower such as Russia.

List what sorts of computer and internet related attacks might we suffer?

destroy their connection to the satellite

DDoS (Denial of Service attack)

Spread out our Intelligence networks for insider attacks

Attack big companies and infrastructure

Mine the government's data

Sabotaging transport, power, food supply communication

Grandma Martha

Activity | Vulnerabilities

Fun and chill exercise to spot where you could possibly explode your oven!!!

Vanilla Cake

180 Deg F?? Should be 180 Deg C

How much cream, sugar butter eggs??

Instructions should be more spread out

Extra stuff: 23x23 means it's square but the picture is a round cake

Cupcakes actually take 12-15 minutes on average, not 20-25

Caramel Slice

100g Extra butter should be at room temerature

Correct method for melting chocolate should be shoulding a double pot.. BUT

Microwave should be 20-30 second intervals, not 1 minute (otherwise the chocolate will burn)

It says PLAISTOWE Dark Chocolate, but it doesn't say that in the ingredients list

2x395 KGS?? Doesn't specify

Recipe doesn't use the golden syrip or condensed milk D:

Cheese Souffle

When it says leave to cool slightly, they really mean turn the heat off

It really should take more than 2/3 cut of milk for a 1.5L dish.

The ratios are wrong from eggs to mixture From another website to make an individual souffle, it uses:

30 mL butter

30 mL flour

175mL milk

Which is roughly a ratio of 1:1:6. However, Martha's recipe here uses:

30 mL butter

60 mL flour

158 mL milk

Which is roughly a ratio of 1:2:5... It's completely wrong.

Week 5 - Secret Case Study

Electric Self-Driven Cars

The premise

You are the the government or the company security head and require to answer 4 slides

1) Assets for the country/company

Citizens and their safety

Sensitive Data

Source code

Reputation

Infrastructure

Jobs + Growth

2) Risks

Privacy of where people go (Is it sent to the government/company

Interception of signals

Accidents

Emergency Manual Takeover

Manual Takover might not work and riders may be controlled as to where they go

Can police intercept if they were chasing a particular car

Who actually owns the cars when something goes wrong

Who is responsible when something goes wrong?

3) Who is responsible for each risk

The company's ethics department

Country has a overlooking manager which deals with company actions

Company takes over from monopoly

4) Are driverless ready for our roads?

The security of driverless cars is not yet confirmed.

The collection of data and what is done with it must be discussed in detail

No secure way os authentication

Conclusion?

Turns out that half the people in the club were talking on behalf of the company whilst the other was talking on behalf of the govenment.

DUN DUN DUNNNN PLOT TWIST.

It was interesting because people talking for the government opposed the idea while people on the compnay's side were strongly pushing for the enforcement of driverless cars.

This case study has successfully allowed us to realise the importance of perspectives and taking into accounts of different interests if stakeholders.

Trending Blogs

Recently Viewed Blogs

itsa jennax