Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

CS 1.4: Designing a safe network: disrupt, detect, limit

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

55 minutes

The shop that went dark for a day

A shop sells online. One cloud company runs its website, its stock list and its tills. The company has an outage. The shop cannot sell anything for a day.

Good design counts on failure and attack. Today you learn three more design goals.

Key words

WordWhat it means
NetworkDevices joined together so they can share data.
MalwareSoftware made to do harm.
ResilienceKeeps working, even in an attack or a failure.
ScalabilityCopes when many more people use it.
BottleneckA tight spot that slows all that comes after it.
Denial of serviceAn attack that floods a system so real users cannot use it.
Third partyAnother firm that you rely on.
Penetration testingA permitted test where an expert tries to break in, to find weaknesses.
SegmentationSplitting a network into parts.
Separation of dutiesSplitting a job so no one person can cause harm alone.
AnonymisationHiding or changing details, so nobody can be named.

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can explain three design goals: make disruption hard, make attacks easy to spot, and limit the harm.

Starter: what you already know

Have a go

Starter: what you already know

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Make disruption difficult

A system must be resilient. It keeps working in an attack or a failure.

Scalability means it copes with a rush of users. Look for any bottleneck. A flood of traffic can block it in a denial of service attack.

Third parties and testing

Find where you rely on a third party. Then plan for it to fail.

Practise. Run mock attacks, so all know what to do. Use outside penetration testing. It makes your rules hard for a real attacker to find.

Make compromise easier to detect

Collect and read security events and logs. They show actions nobody approved.

Set alerts for known malware. Keep the monitoring tools apart from the working systems. Then alerts and logs still work in an attack.

Learn what a normal day looks like. Odd days then stand out.

Check: disrupt and detect

Have a go

Check: disrupt and detect

4 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

The lesson goes on

7 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.