0:00
what do we know about this arrest well
0:02
it's a double development really in the
0:04
last few minutes because not only do we
0:05
now know from the National Crime agency
0:07
that there's been an arrest in this
0:09
Cyber attack we now know more details
0:10
about the attack itself now you'd be
0:12
forgiven for having missed the fact that
0:13
the Cyber attack took place at all it
0:15
was on the first of September it was
0:17
against Transport for London but it
0:18
initially seemed quite minor because no
0:21
transport was actually disrupted and
0:24
tfl's initial statement suggested that
0:26
no customer data had in had been comp
0:29
compromised and today well that changed
0:32
quite dramatically this afternoon in a
0:33
statement from tfl's Chief technology
0:36
officer they said that certain customer
0:39
data has been accessed this includes
0:42
they said some customer names and
0:44
contact details including email
0:45
addresses and home addresses but also
0:48
crucially some Oyster card refund data
0:51
may have been accessed and that might
0:54
include bank account numbers and sort
0:56
codes for what they're describing as a
0:57
limited number of customers now we don't
1:00
yet know the scale of this rest assured
1:02
we will be asking them to see whether we
1:03
can get some more information on how
1:06
widespread it was um but then again in
1:08
the last few minutes the National Crime
1:10
agency who were called in by tfl last
1:12
week to help them deal with us have
1:14
announced that they've arrested a
1:15
17-year-old teenager in Walo in the West
1:18
Midlands now that arrest happened some
1:20
time ago actually on the 5th of
1:22
September uh the teenager was arrested
1:24
on suspicion of offenses under the
1:26
computer misuse act uh and was
1:29
questioned by off officers at the
1:30
National Crime agency and then bailed
1:32
and the NCA says that it's still working
1:34
with tfl to M minimize the any ongoing
1:38
threats from this Cyber attack tfl has
1:41
also said in the statement that they
1:43
would be contacting any customers uh to
1:47
advise them of any next steps they need
1:49
to take but then also they in terms of
1:51
disruption to transport they're
1:52
reassuring people there is no disruption
1:53
to transport but one thing that is
1:55
likely to be affected they say by the
1:57
extra security measures they've had to
1:59
bring in is that on the 22nd of
2:01
September an additional 47 stations
2:04
outside of London were due to be getting
2:06
contactless support so you could
2:07
basically beep in with your card and
2:09
beep out again that has now been delayed
2:11
to an as yet undef undefined date which
2:14
they say is part of the security
2:16
measures they've had to take so no
2:17
transport disruption but potentially
2:19
some quite significant customer data
2:21
breach quite what the scale of it yet is
2:23
we we don't quite know
