﻿WEBVTT

00:00:00.000 --> 00:00:03.486
[MUSIC PLAYING]

00:00:26.940 --> 00:00:28.980
Welcome to Hacker
House Hands-On Hacking.

00:00:28.980 --> 00:00:31.350
This is the first module
in our course, which

00:00:31.350 --> 00:00:32.970
is a purely academic module.

00:00:32.970 --> 00:00:35.350
It's the only academic
module in the course.

00:00:35.350 --> 00:00:38.010
Now, we couldn't give a
course teaching computer

00:00:38.010 --> 00:00:40.560
hacking skills if we
weren't able to focus

00:00:40.560 --> 00:00:44.240
on the legal elements and what
you are lawfully allowed to do.

00:00:50.920 --> 00:00:53.590
So ethics and legalities.

00:00:53.590 --> 00:00:55.540
When we talk about
ethics and legalities,

00:00:55.540 --> 00:00:58.400
ethics can mean different
things to different people.

00:00:58.400 --> 00:01:00.700
And they are very personal
in terms of their regards.

00:01:00.700 --> 00:01:02.590
But when we're talking
about legalities,

00:01:02.590 --> 00:01:04.840
these are a little
bit more set in stone.

00:01:04.840 --> 00:01:07.840
And these are actually the
black-and-white printed laws,

00:01:07.840 --> 00:01:11.860
which you must adhere to and
follow throughout your career,

00:01:11.860 --> 00:01:15.580
or else you'll get a visit from
perhaps this guy in a Batman

00:01:15.580 --> 00:01:17.710
suit at 6 o'clock
in the morning.

00:01:17.710 --> 00:01:19.870
And that could not be
very pleasant for you.

00:01:19.870 --> 00:01:22.390
So we focus on the
ethics and legalities

00:01:22.390 --> 00:01:23.968
from the UK perspective.

00:01:23.968 --> 00:01:25.510
However, whichever
country you are in

00:01:25.510 --> 00:01:29.710
was most likely to have variants
or similarities to these laws.

00:01:29.710 --> 00:01:32.980
So here in the UK, we have the
Computer Misuse Act, the Data

00:01:32.980 --> 00:01:36.370
Protection Act, the Human Rights
Act, the Wireless & Telegraphy

00:01:36.370 --> 00:01:37.120
Act.

00:01:37.120 --> 00:01:39.040
And these are laws
which have been passed,

00:01:39.040 --> 00:01:41.530
which directly impact
the kinds of work

00:01:41.530 --> 00:01:45.040
that you can do as a
cybersecurity practitioner.

00:01:45.040 --> 00:01:47.350
So the Computer Misuse
Act focuses very heavily

00:01:47.350 --> 00:01:49.270
on what you are and
aren't authorized

00:01:49.270 --> 00:01:51.970
to do against somebody's
computers and indeed, your own.

00:01:51.970 --> 00:01:54.910
And also, the Data
Protection Act

00:01:54.910 --> 00:01:58.210
is there, designed to
ensure that information

00:01:58.210 --> 00:02:03.640
is stored in a secure way, and
that it's not being misused.

00:02:03.640 --> 00:02:05.500
Equally, the Human
Rights Act is there

00:02:05.500 --> 00:02:07.450
to protect the individual
and their right

00:02:07.450 --> 00:02:08.870
to personal privacy.

00:02:08.870 --> 00:02:10.870
So if you're targeting
a company and you

00:02:10.870 --> 00:02:13.360
start key-logging
employees and individuals,

00:02:13.360 --> 00:02:16.540
you might be in violation of
perhaps their right to privacy,

00:02:16.540 --> 00:02:19.120
depending on what their
employer has told them

00:02:19.120 --> 00:02:21.570
they can use their
technology and computers for.

00:02:21.570 --> 00:02:23.320
So these are laws you
need to be aware of.

00:02:23.320 --> 00:02:25.570
And equally, the Wireless
& Telegraphy Act.

00:02:25.570 --> 00:02:28.210
If you start attacking
wireless infrastructure,

00:02:28.210 --> 00:02:32.050
you need to be aware of what
the regulations are around that.

00:02:32.050 --> 00:02:35.200
So most countries will
have a variant of this law.

00:02:35.200 --> 00:02:38.410
In fact, a lot of countries
implemented their own computer

00:02:38.410 --> 00:02:42.430
laws, computer misuse laws
based on the information that

00:02:42.430 --> 00:02:44.950
was given from the UK
Computer Misuse Act,

00:02:44.950 --> 00:02:46.540
as it was one of
the first countries

00:02:46.540 --> 00:02:49.420
to successfully prosecute
a computer crime.

00:02:49.420 --> 00:02:51.377
And so the Computer
Misuse Act has

00:02:51.377 --> 00:02:52.960
been used for a lot
of other countries

00:02:52.960 --> 00:02:54.760
as the basis of their law.

00:02:54.760 --> 00:02:56.980
But you may find
that in your country

00:02:56.980 --> 00:03:01.000
there is some slight variance
to the legal aspects compared

00:03:01.000 --> 00:03:02.140
to the UK.

00:03:02.140 --> 00:03:04.500
Equally, there is a Hacker
House Code of Conduct.

00:03:04.500 --> 00:03:06.940
We have supplied the Hacker
House Code of Conduct

00:03:06.940 --> 00:03:09.110
to ensure that everybody
has filled that in.

00:03:09.110 --> 00:03:11.110
Whether you are taking
our course in a classroom

00:03:11.110 --> 00:03:13.210
environment or whether
you are doing this

00:03:13.210 --> 00:03:15.880
at home and the on demand,
the code of conduct

00:03:15.880 --> 00:03:18.820
is there to show you how
we expect our students

00:03:18.820 --> 00:03:20.310
to behave towards each other.

00:03:20.310 --> 00:03:22.330
And we provide a safe
space for learning,

00:03:22.330 --> 00:03:25.330
so that we don't encourage
people to be harassing

00:03:25.330 --> 00:03:28.900
or other intolerable behavior
towards other students

00:03:28.900 --> 00:03:31.120
or indeed, tutors themselves.

00:03:31.120 --> 00:03:34.150
So just please familiar yourself
with your code of conduct,

00:03:34.150 --> 00:03:36.370
because it is something
that we do stress.

00:03:36.370 --> 00:03:38.440
We do want people to have
a good experience when

00:03:38.440 --> 00:03:40.000
they're learning these things.

00:03:40.000 --> 00:03:42.520
We'll also look at responsible
disclosure practices, bug

00:03:42.520 --> 00:03:44.470
bounties, and various
things, and where

00:03:44.470 --> 00:03:47.260
you can get legal
support should you

00:03:47.260 --> 00:03:49.300
encounter some complications.

00:03:55.550 --> 00:03:58.010
So hacking laws and you.

00:03:58.010 --> 00:04:00.530
The thing with the computer
crime laws and computer hacking

00:04:00.530 --> 00:04:03.140
laws is that the penalties
for illegal hacking attacks

00:04:03.140 --> 00:04:04.940
are extremely severe.

00:04:04.940 --> 00:04:08.570
So if you are conducting
illegal, criminal intrusions,

00:04:08.570 --> 00:04:11.660
then you can face quite
severe criminal penalties.

00:04:11.660 --> 00:04:13.160
So it's very important
to understand

00:04:13.160 --> 00:04:14.320
what you can and can't do.

00:04:14.320 --> 00:04:17.480
And generally speaking,
testing your own computers

00:04:17.480 --> 00:04:19.310
that you bought,
you have, you own--

00:04:19.310 --> 00:04:21.589
your property is
more or less lawful.

00:04:21.589 --> 00:04:23.240
There's not really
any laws that cover

00:04:23.240 --> 00:04:24.930
what you can do with that.

00:04:24.930 --> 00:04:27.140
However, if you're
testing your place of work

00:04:27.140 --> 00:04:30.290
or you are testing a neighbor's
computer system or similar,

00:04:30.290 --> 00:04:32.780
then you need to ensure
that you have permission

00:04:32.780 --> 00:04:33.853
from the system owner.

00:04:33.853 --> 00:04:36.020
If you don't have permission
from that system owner,

00:04:36.020 --> 00:04:38.630
then you are most likely
in violation of some law.

00:04:38.630 --> 00:04:42.110
So the scanning of
internet-connected equipment--

00:04:42.110 --> 00:04:43.820
while it's not
technically illegal

00:04:43.820 --> 00:04:46.970
is often frowned upon by
some system administrators.

00:04:46.970 --> 00:04:48.887
So whilst you can scan
the internet for common

00:04:48.887 --> 00:04:51.387
vulnerabilities-- and there are
a number of services that do

00:04:51.387 --> 00:04:52.010
that--

00:04:52.010 --> 00:04:53.930
if you began scanning
systems by yourself,

00:04:53.930 --> 00:04:56.275
you may find that you'll
get abuse complaint reports,

00:04:56.275 --> 00:04:58.400
particularly if you scan
the Department of Defense,

00:04:58.400 --> 00:04:59.360
for instance.

00:04:59.360 --> 00:05:02.150
Then you may receive some emails
indicating that your behavior

00:05:02.150 --> 00:05:03.840
is not welcome.

00:05:03.840 --> 00:05:06.530
And so be cautious
about scanning systems

00:05:06.530 --> 00:05:07.630
without permission.

00:05:07.630 --> 00:05:10.490
And using default passwords
or accessing services

00:05:10.490 --> 00:05:12.750
without permission is
pretty much a gray area.

00:05:12.750 --> 00:05:15.020
Some people claim that
if I connect to a system

00:05:15.020 --> 00:05:17.590
and it lets me straight in,
then there was no password.

00:05:17.590 --> 00:05:18.590
There was no protection.

00:05:18.590 --> 00:05:21.110
And it was therefore a
public access system.

00:05:21.110 --> 00:05:22.870
However, this is
a very gray area.

00:05:22.870 --> 00:05:25.340
And it's very ill advised
and definitely could land you

00:05:25.340 --> 00:05:27.560
in legal trouble in the UK.

00:05:27.560 --> 00:05:29.810
So we stress very hard
that you should always

00:05:29.810 --> 00:05:33.410
seek written permission from
the system owner of the network

00:05:33.410 --> 00:05:35.360
or environment that you
are planning to test--

00:05:35.360 --> 00:05:36.140
very important.

00:05:36.140 --> 00:05:38.990
And it will help save you a
lot of aggravation and stress

00:05:38.990 --> 00:05:40.778
later on in life.

00:05:40.778 --> 00:05:45.590
So when we conduct these kinds
of assessment activities,

00:05:45.590 --> 00:05:47.630
when we start to engage
in kind of hacking for

00:05:47.630 --> 00:05:50.512
hire, or we conduct
a penetration test,

00:05:50.512 --> 00:05:52.970
though we would follow a number
of different methodologies.

00:05:52.970 --> 00:05:54.590
And there are a number
of common methodologies

00:05:54.590 --> 00:05:56.330
which have surfaced
over the years--

00:05:56.330 --> 00:05:59.150
open standards and
guidelines designed

00:05:59.150 --> 00:06:01.990
for how you can conduct
different test activities.

00:06:01.990 --> 00:06:10.650
And there are a few of them
listed on the slides here,

00:06:10.650 --> 00:06:14.290
so the Information Systems
Security Assessment Framework,

00:06:14.290 --> 00:06:16.880
the Penetration Testing
Execution Standard,

00:06:16.880 --> 00:06:19.400
PCI pen testing guide, which
I don't personally think

00:06:19.400 --> 00:06:21.130
is worth the paper
it's printed on,

00:06:21.130 --> 00:06:23.000
the penetration
testing framework,

00:06:23.000 --> 00:06:26.680
and the Open Source Security
Testing Methodology Manual.

00:06:26.680 --> 00:06:29.400
Of these, I really rate the
Penetration Testing Execution

00:06:29.400 --> 00:06:29.900
Standard.

00:06:29.900 --> 00:06:31.670
It contains a lot
of guidance for how

00:06:31.670 --> 00:06:35.180
to conduct an engagement,
how to engage with clients,

00:06:35.180 --> 00:06:36.860
issuance of reporting.

00:06:36.860 --> 00:06:39.650
It does give you a kind
of overall standard of how

00:06:39.650 --> 00:06:41.330
somebody may expect
a penetration

00:06:41.330 --> 00:06:43.400
test to be conducted
and also gives you

00:06:43.400 --> 00:06:46.410
some guidance on how to actually
execute some of those tasks.

00:06:46.410 --> 00:06:49.000
So I really do like
the P test standard.

00:06:49.000 --> 00:06:52.090
Another manual which is
quite worth it is the OSSTMM.

00:06:52.090 --> 00:06:53.840
Although it's a little
longer in the tooth

00:06:53.840 --> 00:06:55.910
now and quite a little
bit out of date,

00:06:55.910 --> 00:06:58.460
you will find that there's a
number of testing methodologies

00:06:58.460 --> 00:07:01.290
written in there for systems
like PBXs or voice mail

00:07:01.290 --> 00:07:01.790
systems.

00:07:01.790 --> 00:07:04.160
And it contains a lot of
different methodologies.

00:07:04.160 --> 00:07:05.930
So you might find
information of value

00:07:05.930 --> 00:07:07.790
to there, when you
start in your career

00:07:07.790 --> 00:07:10.593
if you're testing a
new system or perhaps

00:07:10.593 --> 00:07:12.260
coming across a
technology you might not

00:07:12.260 --> 00:07:15.740
have encountered before for
security audit purposes.

00:07:15.740 --> 00:07:19.530
So P tests and OSSTMMs are the
two that I would recommend.

00:07:19.530 --> 00:07:21.080
Again, they're
not the only ones,

00:07:21.080 --> 00:07:23.150
but they are just some
brilliant ones to follow.

00:07:23.150 --> 00:07:24.650
The penetration
testing framework

00:07:24.650 --> 00:07:25.810
is another good example.

00:07:32.680 --> 00:07:35.503
As we've already explained,
the concept of authorization

00:07:35.503 --> 00:07:36.920
is extremely
important when you're

00:07:36.920 --> 00:07:39.087
dealing with computer
security and particularly when

00:07:39.087 --> 00:07:41.030
you're doing these kind
of hacking activities.

00:07:41.030 --> 00:07:45.440
It is imperative that a system
owner approves your activities.

00:07:45.440 --> 00:07:48.470
If you do not have authority
to test a computer system,

00:07:48.470 --> 00:07:50.810
you are potentially
committing a criminal offense.

00:07:50.810 --> 00:07:53.970
And as I've said before, the
penalties are quite severe.

00:07:53.970 --> 00:07:57.290
So please get us a signed copy
of an authorization for testing

00:07:57.290 --> 00:07:59.660
contracts in place
with any system owner

00:07:59.660 --> 00:08:02.330
before you begin
conducting any testing

00:08:02.330 --> 00:08:03.890
or any kind of experiments.

00:08:03.890 --> 00:08:06.650
And indeed, this should clearly
state that they will not

00:08:06.650 --> 00:08:09.410
seek to prosecute you under
the Computer Misuse Act

00:08:09.410 --> 00:08:12.590
to avoid any further
or future confusion.

00:08:12.590 --> 00:08:14.757
And the best piece of advice
I can give you, really,

00:08:14.757 --> 00:08:16.673
when you're conducting
this kind of assessment

00:08:16.673 --> 00:08:19.520
is to just be very transparent
and open about your activities

00:08:19.520 --> 00:08:21.655
and always get permission
before doing them.

00:08:21.655 --> 00:08:23.780
You will avoid a lot of
complications and headaches

00:08:23.780 --> 00:08:26.180
if you are just very open
about the type of testing

00:08:26.180 --> 00:08:26.810
you're doing.

00:08:26.810 --> 00:08:29.300
I'm going to assess
this web server today.

00:08:29.300 --> 00:08:31.470
I'm going to launch
this exploit later on.

00:08:31.470 --> 00:08:33.679
There may be a risk
to that system.

00:08:33.679 --> 00:08:35.659
And the system owner
might say, please

00:08:35.659 --> 00:08:38.630
only conduct that outside
of office hours at 6:00 PM.

00:08:38.630 --> 00:08:41.210
Or there may be some
window of which they

00:08:41.210 --> 00:08:44.720
would prefer you to conduct
those more dangerous elements

00:08:44.720 --> 00:08:45.680
of the assessment.

00:08:45.680 --> 00:08:47.900
So, yes, always ensure
you've got permission

00:08:47.900 --> 00:08:50.390
and be transparent and
open with the system owner.

00:08:50.390 --> 00:08:53.870
Be clear and concise and
explain to them what's going on.

00:08:53.870 --> 00:08:55.340
Because at the end
of the day, you

00:08:55.340 --> 00:08:56.570
are a guest on their network.

00:08:56.570 --> 00:08:58.130
You're a guest in
their environment.

00:08:58.130 --> 00:08:59.450
And you should be--

00:08:59.450 --> 00:09:01.907
you should treat their network
and environment as such.

00:09:08.370 --> 00:09:12.150
Another concept which is
quite commonly discussed

00:09:12.150 --> 00:09:14.470
is the concept of disclosure.

00:09:14.470 --> 00:09:18.048
So whilst you are conducting
your information security-type

00:09:18.048 --> 00:09:19.590
jobs, you are doing
your pen testing.

00:09:19.590 --> 00:09:21.000
You find a vulnerability.

00:09:21.000 --> 00:09:22.740
And you find this
vulnerability impacts

00:09:22.740 --> 00:09:24.690
not just your
client, but also all

00:09:24.690 --> 00:09:26.160
of the users of that software.

00:09:26.160 --> 00:09:27.540
It's a new kind of attack.

00:09:27.540 --> 00:09:30.660
It's a new kind of exploit and
therefore known as a zero day

00:09:30.660 --> 00:09:33.690
or a zero-day attack, a
previously unknown security

00:09:33.690 --> 00:09:36.240
flaw that may require
intervention or software

00:09:36.240 --> 00:09:37.590
update from a vendor.

00:09:37.590 --> 00:09:40.260
And the concept of
responsible disclosure

00:09:40.260 --> 00:09:43.710
is the practice of
working with that vendor

00:09:43.710 --> 00:09:46.980
to resolve the vulnerability
and protect the consumers.

00:09:46.980 --> 00:09:49.410
So the industry de
facto guidelines suggest

00:09:49.410 --> 00:09:51.840
that we give a 90-day
window of opportunity

00:09:51.840 --> 00:09:54.760
to allow for patching, so
you contact the vendor.

00:09:54.760 --> 00:09:57.420
You allow them 90 days
to implement the fix.

00:09:57.420 --> 00:09:59.880
After a fix has been
supplied of the 90 days,

00:09:59.880 --> 00:10:04.890
allow a further 30 days for
customers to obtain that fix,

00:10:04.890 --> 00:10:08.010
apply it to their
servers before disclosing

00:10:08.010 --> 00:10:11.300
details of the exploit and the
analysis that were conducted.

00:10:11.300 --> 00:10:13.380
And indeed, some vendors
will reward your efforts

00:10:13.380 --> 00:10:14.410
in a hall of fame.

00:10:14.410 --> 00:10:18.510
Or those may be less
rewarding and may not

00:10:18.510 --> 00:10:20.730
be as happy to have
vulnerabilities

00:10:20.730 --> 00:10:21.772
in their products.

00:10:21.772 --> 00:10:23.730
But if you stick to this
responsible disclosure

00:10:23.730 --> 00:10:26.880
guideline, give them 90
days and a further 30 days

00:10:26.880 --> 00:10:30.040
after a patch is released
before disclosing.

00:10:30.040 --> 00:10:31.960
And if the vendor
doesn't wish to disclose

00:10:31.960 --> 00:10:34.080
or doesn't wish to work
with you on that point,

00:10:34.080 --> 00:10:36.630
then at that point, it would
be OK to share the information

00:10:36.630 --> 00:10:39.060
with the wider community
and effectively force

00:10:39.060 --> 00:10:41.610
the hand of the vendor to
acknowledge the problem

00:10:41.610 --> 00:10:44.580
and address the issue to
protect its consumers.

00:10:44.580 --> 00:10:46.980
Because you have also
a moral obligation

00:10:46.980 --> 00:10:49.920
to protect the impacted
policies of the software,

00:10:49.920 --> 00:10:51.750
not just the vendor
and their reputation.

00:10:58.210 --> 00:11:00.310
So that brings us
to bug bounties.

00:11:00.310 --> 00:11:02.860
Bug bounties are programs
which are established

00:11:02.860 --> 00:11:06.040
by organizations, so that
they can receive vulnerability

00:11:06.040 --> 00:11:09.220
or information from
the public that

00:11:09.220 --> 00:11:12.412
can then be used to address
those bugs and vulnerabilities.

00:11:12.412 --> 00:11:13.870
So it's actually
a way of you being

00:11:13.870 --> 00:11:17.530
able to conduct penetration
tests against organizations

00:11:17.530 --> 00:11:19.840
and gain some kind of
commercial experience

00:11:19.840 --> 00:11:22.717
for the processes involved in
reporting of vulnerability.

00:11:22.717 --> 00:11:24.550
And indeed, if you are
successful in finding

00:11:24.550 --> 00:11:27.250
weaknesses, you can indeed
get some monetary rewards

00:11:27.250 --> 00:11:28.250
for your efforts.

00:11:28.250 --> 00:11:31.060
And now, you need to ensure when
you are conducting assessments

00:11:31.060 --> 00:11:33.910
against bug bounty programs
that you fully review the terms

00:11:33.910 --> 00:11:37.750
and conditions of that program
and that you don't end up

00:11:37.750 --> 00:11:39.138
overstepping the scope.

00:11:39.138 --> 00:11:40.930
You need to ensure that
your activities are

00:11:40.930 --> 00:11:44.230
within the scope of the
program, so that you do not

00:11:44.230 --> 00:11:49.390
inadvertently expose yourself
to any kind of legal risk.

00:11:49.390 --> 00:11:51.580
And what I mean by
that is as an example,

00:11:51.580 --> 00:11:53.530
though as a bug
bounty of Facebook--

00:11:53.530 --> 00:11:56.500
and an individual breached
the Facebook server

00:11:56.500 --> 00:11:59.830
and then continued to operate
outside of the scope of the bug

00:11:59.830 --> 00:12:03.730
bounty program by accessing
internal Facebook services

00:12:03.730 --> 00:12:06.610
and querying information
on Facebook users.

00:12:06.610 --> 00:12:09.370
And subsequently, when he
submitted his bug report,

00:12:09.370 --> 00:12:11.930
instead of a monetary award,
Facebook arrested him.

00:12:11.930 --> 00:12:14.680
So you need to ensure that
whenever you are conducting

00:12:14.680 --> 00:12:16.630
these kinds of bug
bounty programs,

00:12:16.630 --> 00:12:19.000
review the terms and
conditions and ensure

00:12:19.000 --> 00:12:21.610
that any activity you
do is within the scope

00:12:21.610 --> 00:12:22.250
of the program.

00:12:22.250 --> 00:12:25.975
If it says do not go
targeting admin.company.com,

00:12:25.975 --> 00:12:28.930
then ensure that you
don't target those systems

00:12:28.930 --> 00:12:29.898
and servers.

00:12:29.898 --> 00:12:31.940
If you are worried about
overstepping a boundary,

00:12:31.940 --> 00:12:33.607
you feel like you
might be operating out

00:12:33.607 --> 00:12:35.632
of the scope of a
program, the best thing

00:12:35.632 --> 00:12:37.340
to do is to check with
the program owner.

00:12:37.340 --> 00:12:39.560
It comes back to that
openness and transparenceness

00:12:39.560 --> 00:12:41.935
as long as you are open and
transparent about these kinds

00:12:41.935 --> 00:12:43.900
of tests and these
assessment activities

00:12:43.900 --> 00:12:47.140
and you are doing things within
scopes of bug bounty programs.

00:12:47.140 --> 00:12:48.940
And being open and
transparent will

00:12:48.940 --> 00:12:50.770
get you-- clear a
lot of confusion

00:12:50.770 --> 00:12:53.793
and make sure there's no
complications down the road.

00:12:53.793 --> 00:12:55.210
It can be quite
an intrusive thing

00:12:55.210 --> 00:12:57.400
when you are breaching
into networks and systems.

00:12:57.400 --> 00:12:59.550
So you need to ensure that
when you are doing that

00:12:59.550 --> 00:13:03.040
and you're using these intrusive
powers that you respect

00:13:03.040 --> 00:13:05.620
the rules and the
scopes of any programs

00:13:05.620 --> 00:13:07.520
that you might be involved in.

00:13:07.520 --> 00:13:09.560
And most of all, have fun.

00:13:09.560 --> 00:13:12.490
It's an enjoyable and profitable
pastime for many people

00:13:12.490 --> 00:13:14.180
to get involved in bug bounties.

00:13:14.180 --> 00:13:15.820
And so it's a great
way for you to get

00:13:15.820 --> 00:13:16.960
some commercial experience.

00:13:16.960 --> 00:13:18.790
It certainly helps
the interview stage

00:13:18.790 --> 00:13:20.740
when you are being shown--

00:13:20.740 --> 00:13:22.580
when you're showing how
you have progressed,

00:13:22.580 --> 00:13:25.180
all the things that you can
do, to show and demonstrate

00:13:25.180 --> 00:13:28.412
some kind of capacity
and skills in this area

00:13:28.412 --> 00:13:30.370
if you're just trying to
get into the industry.

00:13:30.370 --> 00:13:32.200
So bug bounties are
a great way for you

00:13:32.200 --> 00:13:35.830
to get some experience on this
kind of assessment activities.

00:13:42.390 --> 00:13:44.970
What happens should
you ever find yourself

00:13:44.970 --> 00:13:46.350
in a legal predicament?

00:13:46.350 --> 00:13:49.110
So if you do need legal
advice and support,

00:13:49.110 --> 00:13:51.210
I can assure you cyber
and cybercrime lawyers

00:13:51.210 --> 00:13:52.840
are really expensive.

00:13:52.840 --> 00:13:56.820
And I mean, seriously,
lawyers are really expensive.

00:13:56.820 --> 00:13:59.650
They can cost upwards
of $1,000 an hour,

00:13:59.650 --> 00:14:01.583
depending on the level
of advice that you need

00:14:01.583 --> 00:14:03.500
and the legal system
that you're working with.

00:14:03.500 --> 00:14:05.010
So be aware.

00:14:05.010 --> 00:14:06.400
Lawyers are really expensive.

00:14:06.400 --> 00:14:09.150
So you want to avoid using
them as best as possible.

00:14:09.150 --> 00:14:12.060
If you do, however, find
yourself in a situation

00:14:12.060 --> 00:14:14.010
where you might
need legal advice,

00:14:14.010 --> 00:14:16.360
then you could get in contact
with two organizations.

00:14:16.360 --> 00:14:18.280
One is the Electronic
Frontier Foundation,

00:14:18.280 --> 00:14:20.280
who could put you in touch
with some lawyers who

00:14:20.280 --> 00:14:21.990
specialize in cyber.

00:14:21.990 --> 00:14:25.470
And also, EDRI, which is
the European equivalent, who

00:14:25.470 --> 00:14:28.320
can also help find you
support or legal practitioners

00:14:28.320 --> 00:14:32.730
that are well versed in
cyber and EU-related laws.

00:14:32.730 --> 00:14:34.500
The best advice that
can be given to you

00:14:34.500 --> 00:14:36.750
is if you are
arrested or experience

00:14:36.750 --> 00:14:39.930
any kind of complications, then
seek professional legal advice

00:14:39.930 --> 00:14:43.350
immediately and do not answer
any questions before consulting

00:14:43.350 --> 00:14:45.600
a qualified legal professional.

00:14:45.600 --> 00:14:47.423
I am not a legal professional.

00:14:47.423 --> 00:14:49.590
And I would advise you that
should you find yourself

00:14:49.590 --> 00:14:52.320
in a situation where you
need a legal professional,

00:14:52.320 --> 00:14:55.140
speak to the legal professional,
and don't answer any questions

00:14:55.140 --> 00:14:58.560
or speak to anybody else,
and only operate and follow

00:14:58.560 --> 00:15:00.270
the advice of the
legal practitioners.

00:15:00.270 --> 00:15:01.770
And it's very
important that you get

00:15:01.770 --> 00:15:04.650
one that is well versed
in the world of cyber,

00:15:04.650 --> 00:15:07.500
as it is quite confusing
for many legislators.

00:15:07.500 --> 00:15:10.525
And there are often miscarriages
of justice in this space.

00:15:10.525 --> 00:15:11.400
So that's what to do.

00:15:11.400 --> 00:15:12.810
If you do encounter
any problems,

00:15:12.810 --> 00:15:16.800
get in touch with the EFF or
EDRI, depending on your region,

00:15:16.800 --> 00:15:19.860
to find a well-versed
cyber practitioner who

00:15:19.860 --> 00:15:21.090
can help you with the law.

00:15:27.920 --> 00:15:30.740
Equally, Hacker House
has its code of conduct.

00:15:30.740 --> 00:15:32.960
And if you take our
course, then you

00:15:32.960 --> 00:15:34.737
must have agreed to
our code of conduct,

00:15:34.737 --> 00:15:37.070
because we're going to be
teaching you real-world attack

00:15:37.070 --> 00:15:39.395
techniques that you could
use to commit criminal acts.

00:15:39.395 --> 00:15:41.270
And Hacker House will
not be held accountable

00:15:41.270 --> 00:15:42.110
for such actions.

00:15:42.110 --> 00:15:44.240
We teach you these
skills to show you

00:15:44.240 --> 00:15:46.100
how computer systems
are broken, so

00:15:46.100 --> 00:15:49.138
that we can understand how to
better defend those systems.

00:15:49.138 --> 00:15:50.930
We'll show you how
systems can be breached.

00:15:50.930 --> 00:15:52.555
We'll show you the
tools and techniques

00:15:52.555 --> 00:15:56.010
used by computer hackers
for many different reasons.

00:15:56.010 --> 00:15:59.000
And you could use these
in a nefarious way.

00:15:59.000 --> 00:16:01.280
But we will teach
only people who

00:16:01.280 --> 00:16:04.900
intend to follow industry de
facto best practice guidelines.

00:16:04.900 --> 00:16:07.310
And we will only
teach people who

00:16:07.310 --> 00:16:09.140
agree to our code of conduct.

00:16:09.140 --> 00:16:12.260
And we'll be performing
ethical hacking activities

00:16:12.260 --> 00:16:15.652
within a legal way.

00:16:15.652 --> 00:16:17.360
And ignoring these
guidelines, of course,

00:16:17.360 --> 00:16:19.270
can lead to legal
problems for you.

00:16:19.270 --> 00:16:20.870
And so please
familiarize yourself

00:16:20.870 --> 00:16:23.090
with our code of conduct,
whether you're at home

00:16:23.090 --> 00:16:24.920
or whether you are
in our classroom

00:16:24.920 --> 00:16:31.030
to ensure that you are following
your expected behavior.

00:16:31.030 --> 00:16:32.600
And that kind of
brings me nicely

00:16:32.600 --> 00:16:34.260
to the end of this module.

00:16:34.260 --> 00:16:35.970
So it is the only
academic theory module.

00:16:35.970 --> 00:16:37.790
So for this module,
all I need you to do

00:16:37.790 --> 00:16:40.520
is familiarize yourself with
any differences in the law.

00:16:40.520 --> 00:16:42.740
If you're in America, for
instance, the Computer

00:16:42.740 --> 00:16:44.120
Fraud and Abuse Act.

00:16:44.120 --> 00:16:46.220
And some of the Digital
Millennium Copyright

00:16:46.220 --> 00:16:49.760
Act and other laws will
also be applicable to you.

00:16:49.760 --> 00:16:52.670
This, of course, has a
UK-centric area of the law,

00:16:52.670 --> 00:16:55.020
so the Computer Misuse Act
being the main one here.

00:16:55.020 --> 00:16:58.250
And most of these laws require
you to seek permission,

00:16:58.250 --> 00:16:59.690
so it's important to understand.

00:16:59.690 --> 00:17:00.980
Always get permission.

00:17:00.980 --> 00:17:03.350
Always work within the
scope of any program.

00:17:03.350 --> 00:17:06.170
And always be open and
transparent with system owners

00:17:06.170 --> 00:17:08.780
to avoid any confusion
and complications.

00:17:08.780 --> 00:17:09.349
Thank you.

00:17:09.349 --> 00:17:12.699
[MUSIC PLAYING]
