1 00:00:05,640 --> 00:00:08,960 Speaker 1: Kielder. I'm Chelsea Daniels and this is the Front Page, 2 00:00:09,400 --> 00:00:17,560 Speaker 1: a daily podcast presented by the New Zealand Herald. Our 3 00:00:17,840 --> 00:00:22,480 Speaker 1: y two k bug fears became a reality when millions 4 00:00:22,520 --> 00:00:27,840 Speaker 1: of computers were disabled worldwide over the weekend. Microsoft estimates 5 00:00:27,920 --> 00:00:32,600 Speaker 1: the outage meant eight point five million computers were disabled 6 00:00:33,000 --> 00:00:42,279 Speaker 1: when an update from global cybersecurity company CrowdStrike went wrong. Banks, airports, supermarkets, 7 00:00:42,320 --> 00:00:46,640 Speaker 1: media companies and retailers were left scrambling, and the company's 8 00:00:46,680 --> 00:00:50,559 Speaker 1: chief executive says it could be some time before systems 9 00:00:50,600 --> 00:00:55,440 Speaker 1: are completely back to normal. It's believed to have been 10 00:00:55,480 --> 00:00:59,680 Speaker 1: the biggest tech outage in history. So what can we 11 00:00:59,760 --> 00:01:02,640 Speaker 1: learn from this to prevent it from happening again? And 12 00:01:02,720 --> 00:01:07,000 Speaker 1: does it expose weaknesses in a globally connected computer network. 13 00:01:07,560 --> 00:01:10,520 Speaker 1: Today on the Front Page, to analyze the next steps 14 00:01:10,560 --> 00:01:15,160 Speaker 1: from this tech crisis, we're joined by Aura Information Security 15 00:01:15,200 --> 00:01:25,679 Speaker 1: advisory consultant Alistair Miller. Alistair, what was your reaction on 16 00:01:25,760 --> 00:01:29,120 Speaker 1: Friday night when these problems started to be reported globally. 17 00:01:29,520 --> 00:01:31,680 Speaker 2: I have to say I was a bit worried for 18 00:01:31,720 --> 00:01:33,160 Speaker 2: all the IT teams who are going to have to 19 00:01:33,160 --> 00:01:35,880 Speaker 2: deal with them. As the problems escalated and as we've 20 00:01:35,920 --> 00:01:39,160 Speaker 2: now found out, it's least eight point five million computers. 21 00:01:39,240 --> 00:01:40,920 Speaker 2: That's a lot of work for a lot of people 22 00:01:40,959 --> 00:01:41,560 Speaker 2: to sort out. 23 00:01:41,880 --> 00:01:45,200 Speaker 1: This issue has been blamed on a software update, but 24 00:01:45,280 --> 00:01:49,080 Speaker 1: the effects were pretty wide spread. Planes were canceled, banking 25 00:01:49,120 --> 00:01:53,120 Speaker 1: systems where inaccessible security systems went down. The list goes on. 26 00:01:53,200 --> 00:01:57,040 Speaker 1: How standard is it that so many different and varied 27 00:01:57,200 --> 00:02:00,880 Speaker 1: systems and industries would be linked to the same software. 28 00:02:01,400 --> 00:02:02,800 Speaker 3: Unfortunately, it's quite common. 29 00:02:03,000 --> 00:02:05,800 Speaker 2: There's a sort of only a small handful of big 30 00:02:05,840 --> 00:02:09,160 Speaker 2: players in a lot of the IT spaces, and they 31 00:02:10,200 --> 00:02:13,280 Speaker 2: pretty much cover all especially crowdstrikes at the top end 32 00:02:13,320 --> 00:02:14,960 Speaker 2: of the market. So that will be with all those 33 00:02:14,960 --> 00:02:18,840 Speaker 2: big players, those banks, big transport companies who we probably 34 00:02:18,880 --> 00:02:21,160 Speaker 2: haven't seen in the press but probably have suffered because 35 00:02:21,200 --> 00:02:24,079 Speaker 2: it's going to take a bit longer there and other 36 00:02:24,200 --> 00:02:26,760 Speaker 2: big players are going to be impacted by those things. 37 00:02:29,760 --> 00:02:34,920 Speaker 4: The scale of the outage unprecedented, affecting flights, banks, healthcare systems, 38 00:02:34,960 --> 00:02:38,840 Speaker 4: and TV stations. The trouble first occurred in Australia and 39 00:02:38,880 --> 00:02:42,679 Speaker 4: here industries hit in America, across Europe and Asia. 40 00:02:42,560 --> 00:02:46,600 Speaker 3: Chaos for airlines there are canceled Amy drive. 41 00:02:46,960 --> 00:02:49,240 Speaker 5: We'll have to try and get a flying home somewhere 42 00:02:49,440 --> 00:02:51,280 Speaker 5: somewhere sometime, don't know. 43 00:02:51,720 --> 00:02:56,600 Speaker 3: Sint John lost computers for taking calls and for dispatching. 44 00:02:56,440 --> 00:03:00,359 Speaker 4: Literally a paper process, having to go back to writing 45 00:03:00,360 --> 00:03:06,280 Speaker 4: things and using paper and paper boat system. 46 00:03:06,560 --> 00:03:09,960 Speaker 1: We know the issues being traced back to CrowdStrike, a 47 00:03:10,000 --> 00:03:14,440 Speaker 1: company that produces anti virus software. You mentioned with eight 48 00:03:14,480 --> 00:03:19,560 Speaker 1: point five million Microsoft devices affected. What do you think 49 00:03:19,639 --> 00:03:20,480 Speaker 1: went wrong here? 50 00:03:20,960 --> 00:03:23,280 Speaker 2: It appears it's a bit of a lack of quality assurance, 51 00:03:23,360 --> 00:03:26,320 Speaker 2: so they didn't do their testing with the latest Microsoft 52 00:03:26,400 --> 00:03:29,680 Speaker 2: update and released a bit of software that conflicted badly 53 00:03:29,760 --> 00:03:32,880 Speaker 2: with the Microsoft update and took all those PCs and 54 00:03:32,919 --> 00:03:33,799 Speaker 2: servers out. 55 00:03:33,800 --> 00:03:37,800 Speaker 1: And CrowdStrike I believe has around a twenty percent market share. 56 00:03:38,000 --> 00:03:42,000 Speaker 1: Is this one example where one company being so dominant 57 00:03:42,040 --> 00:03:44,720 Speaker 1: in the market really doesn't work in people's favor. 58 00:03:45,360 --> 00:03:48,040 Speaker 2: Well, I mean there is that risk, and again they 59 00:03:48,120 --> 00:03:50,360 Speaker 2: cater to the high end market, so the ones who 60 00:03:50,400 --> 00:03:53,680 Speaker 2: are much more noticeable. But it's just very common in 61 00:03:53,720 --> 00:03:56,120 Speaker 2: the IT space where there are a few big players 62 00:03:56,640 --> 00:04:00,480 Speaker 2: who can dominate the markets and then obviously when run 63 00:04:00,480 --> 00:04:04,200 Speaker 2: into trouble, it hits everyone. I mean, Microsoft and Amazon 64 00:04:04,240 --> 00:04:07,520 Speaker 2: are the prime example really with who the biggest cloud 65 00:04:07,520 --> 00:04:10,040 Speaker 2: providers adding Google not so big in New Zealand, but 66 00:04:10,080 --> 00:04:13,280 Speaker 2: big worldwide. When they have issues, the whole world feels 67 00:04:13,280 --> 00:04:19,120 Speaker 2: that pain. CrowdStrike is the company behind the software that 68 00:04:19,240 --> 00:04:20,840 Speaker 2: brought everything down. 69 00:04:21,240 --> 00:04:25,000 Speaker 1: We're deeply sorry for the impact that we've caused customers, 70 00:04:25,200 --> 00:04:28,600 Speaker 1: to travelers, to anyone affected by this, including our companies. 71 00:04:28,640 --> 00:04:31,360 Speaker 1: So we know what the issue is. We're resolving and 72 00:04:31,400 --> 00:04:32,440 Speaker 1: have resolved the issue. 73 00:04:32,440 --> 00:04:32,600 Speaker 2: Now. 74 00:04:36,240 --> 00:04:39,440 Speaker 1: Is this really our y two k fears realized twenty 75 00:04:39,440 --> 00:04:40,320 Speaker 1: four years later? 76 00:04:40,839 --> 00:04:43,440 Speaker 2: It certainly demonstrates that the people who put in that 77 00:04:43,520 --> 00:04:46,200 Speaker 2: hard work back then for y two k, this is 78 00:04:46,240 --> 00:04:48,279 Speaker 2: what they were trying to mitigate, these kind of issues 79 00:04:48,320 --> 00:04:50,919 Speaker 2: where it takes down all kinds of systems and things 80 00:04:50,920 --> 00:04:53,800 Speaker 2: that you didn't necessarily expect cause you a lot of pain. 81 00:04:54,080 --> 00:04:56,800 Speaker 1: We were talking on this podcast actually last week about 82 00:04:56,920 --> 00:04:59,560 Speaker 1: if we need to break up the banking sector or 83 00:04:59,560 --> 00:05:03,480 Speaker 1: SuperM it's locally for more competition. Is that something that's 84 00:05:03,720 --> 00:05:06,480 Speaker 1: even possible in the tech sector, or do you need 85 00:05:06,760 --> 00:05:11,120 Speaker 1: a large company like CrowdStrike, say, to actually have the 86 00:05:11,160 --> 00:05:14,400 Speaker 1: capacity to manage millions of devices globally? 87 00:05:14,920 --> 00:05:16,320 Speaker 3: They have a lot of competitors. 88 00:05:16,400 --> 00:05:18,920 Speaker 2: I think our problems are more people have not got 89 00:05:18,960 --> 00:05:22,599 Speaker 2: good business continuity and disaster response plans. A lot of 90 00:05:22,600 --> 00:05:25,520 Speaker 2: New Zealand businesses have nothing, and the ones that a 91 00:05:25,560 --> 00:05:27,240 Speaker 2: lot of the other ones will have something written on 92 00:05:27,279 --> 00:05:29,560 Speaker 2: a piece of paper that's never been exercised at all. 93 00:05:30,200 --> 00:05:33,880 Speaker 2: So people actually prepared for problems happening, because we'll know 94 00:05:34,040 --> 00:05:36,200 Speaker 2: they do. You know, we have COVID, we have earthquakes. 95 00:05:36,320 --> 00:05:37,800 Speaker 2: I mean, you have plans for you know, a fire 96 00:05:37,920 --> 00:05:40,560 Speaker 2: escape and you practice that drill once a year. So 97 00:05:40,800 --> 00:05:43,760 Speaker 2: companies have to have plans for what happens if we 98 00:05:43,800 --> 00:05:46,200 Speaker 2: lose all our servers and how do we get around that? 99 00:05:46,760 --> 00:05:50,120 Speaker 1: So is this really an issue with companies worldwide not 100 00:05:50,279 --> 00:05:52,400 Speaker 1: having those fire escape drills? 101 00:05:52,440 --> 00:05:53,360 Speaker 3: Say it is? 102 00:05:53,600 --> 00:05:55,400 Speaker 2: I mean, I think we'll find that some of them 103 00:05:55,400 --> 00:05:58,200 Speaker 2: have recovered within twenty four to forty eight hours, other 104 00:05:58,200 --> 00:05:59,919 Speaker 2: ones will drag on for weeks, and the ones that 105 00:06:00,040 --> 00:06:02,440 Speaker 2: dragon for weeks will be the ones without the good plans. 106 00:06:03,200 --> 00:06:06,679 Speaker 1: Does New Zealand have any companies based here that could 107 00:06:06,680 --> 00:06:08,720 Speaker 1: take on some of this workload. 108 00:06:08,560 --> 00:06:11,160 Speaker 2: To try and fix it all manually. I mean, we 109 00:06:11,520 --> 00:06:14,360 Speaker 2: New Zealand has an IT skill shortage, which is one 110 00:06:14,360 --> 00:06:16,000 Speaker 2: of the reasons why some companies are going to take 111 00:06:16,000 --> 00:06:17,599 Speaker 2: a long time to recover because they're going to be 112 00:06:17,600 --> 00:06:21,640 Speaker 2: looking to outside providers. But I mean all companies can 113 00:06:21,680 --> 00:06:24,480 Speaker 2: either talk to themselves or talk to consultancies and other 114 00:06:24,520 --> 00:06:27,680 Speaker 2: experts in the area to get advice on what is 115 00:06:27,720 --> 00:06:30,159 Speaker 2: a good business continuity or disaster response plan. 116 00:06:41,080 --> 00:06:45,279 Speaker 1: I've seen the term single point failure emerge in some 117 00:06:45,360 --> 00:06:47,960 Speaker 1: of our analysis of this. Can you explain what that 118 00:06:48,040 --> 00:06:48,680 Speaker 1: actually is? 119 00:06:49,080 --> 00:06:51,640 Speaker 2: So, a single point of failure, or as people lovingly 120 00:06:51,680 --> 00:06:55,560 Speaker 2: call it, a spoff, is basically where everything points to 121 00:06:55,600 --> 00:06:58,480 Speaker 2: one thing. Often in an organization, it can be a person. 122 00:06:58,880 --> 00:07:03,279 Speaker 2: When that person is everything grinds to a halt. It's 123 00:07:03,320 --> 00:07:06,040 Speaker 2: that one place where, even if you had multiple things 124 00:07:06,160 --> 00:07:08,760 Speaker 2: around it, they all have to deal with that system, 125 00:07:08,839 --> 00:07:11,480 Speaker 2: talk to that person or get sort of channeled through it, 126 00:07:11,960 --> 00:07:15,040 Speaker 2: and when that goes down, the whole business goes down 127 00:07:15,080 --> 00:07:17,720 Speaker 2: with it. In this case, it's not quite a single 128 00:07:17,760 --> 00:07:21,080 Speaker 2: point of failure, but it's the inability to have a 129 00:07:21,120 --> 00:07:24,080 Speaker 2: failover for when that thing fails that's more of the 130 00:07:24,160 --> 00:07:25,040 Speaker 2: issue in this case. 131 00:07:26,000 --> 00:07:29,880 Speaker 1: How vulnerable are global systems to these types of issues? 132 00:07:29,920 --> 00:07:33,480 Speaker 1: Does this make us more susceptible to hackers or malicious attacks. 133 00:07:34,040 --> 00:07:37,200 Speaker 2: Indirectly, it may well do where people lose the ability 134 00:07:37,240 --> 00:07:39,640 Speaker 2: to monitor things and see what's going on on a 135 00:07:39,640 --> 00:07:40,320 Speaker 2: wider scale. 136 00:07:40,360 --> 00:07:42,800 Speaker 3: For the issues. Obviously, the attackers. 137 00:07:42,360 --> 00:07:45,120 Speaker 2: Immediately jumped on it, and we're looking to scam people 138 00:07:45,120 --> 00:07:48,400 Speaker 2: with fake websites, fake emails of help and things like that. 139 00:07:49,000 --> 00:07:51,520 Speaker 2: But I think what it really reflects is how interconnected 140 00:07:51,520 --> 00:07:54,080 Speaker 2: the world is nowadays, how much we depend on our 141 00:07:54,120 --> 00:07:56,840 Speaker 2: IT systems, and we need them to be resilient and 142 00:07:56,960 --> 00:07:58,720 Speaker 2: robust to cope with things like this. 143 00:08:00,960 --> 00:08:03,920 Speaker 5: We've been long encouraged to keep our devices software up 144 00:08:03,920 --> 00:08:06,440 Speaker 5: to date, but there are now tough questions as to 145 00:08:06,480 --> 00:08:10,520 Speaker 5: how one faulty update could have brought so much chaos. 146 00:08:11,040 --> 00:08:13,800 Speaker 5: To be clear, this wasn't a hack or cyber attack, 147 00:08:14,160 --> 00:08:17,559 Speaker 5: so you don't need to change any passwords. It only 148 00:08:17,640 --> 00:08:21,800 Speaker 5: affected machines running Microsoft, but every single one will need 149 00:08:21,840 --> 00:08:25,720 Speaker 5: a manual reboot in safe mode. Microsoft says some people 150 00:08:25,920 --> 00:08:28,480 Speaker 5: have to do this as many as fifteen times. 151 00:08:31,320 --> 00:08:34,440 Speaker 1: For years now, we've all been talking about society moving 152 00:08:34,600 --> 00:08:39,160 Speaker 1: more and more online. Do you think this incident will 153 00:08:39,160 --> 00:08:41,679 Speaker 1: make some governments and companies stop and have a bit 154 00:08:41,679 --> 00:08:42,400 Speaker 1: of a rethink. 155 00:08:42,679 --> 00:08:44,240 Speaker 2: Well, I mean, I think they'll have a think about 156 00:08:44,280 --> 00:08:46,199 Speaker 2: it and they'll have to consider what to do. I 157 00:08:46,280 --> 00:08:49,360 Speaker 2: mean often a good business continuity plan is to have 158 00:08:49,480 --> 00:08:52,720 Speaker 2: some paper and some forms available, tell your staff about 159 00:08:52,720 --> 00:08:55,040 Speaker 2: it train the minute, and when the computers go down, 160 00:08:55,080 --> 00:08:57,160 Speaker 2: they go back to those pieces of paper and carry 161 00:08:57,160 --> 00:08:59,440 Speaker 2: on in a sort of more outdated world. But at 162 00:08:59,520 --> 00:09:01,400 Speaker 2: least they know what they're doing and they know how 163 00:09:01,440 --> 00:09:01,800 Speaker 2: to do it. 164 00:09:02,400 --> 00:09:02,600 Speaker 3: Yeah. 165 00:09:02,600 --> 00:09:05,120 Speaker 1: I saw in some supermarkets they actually had those things 166 00:09:05,120 --> 00:09:05,840 Speaker 1: that we used. 167 00:09:05,640 --> 00:09:08,120 Speaker 3: To have and yeah, the little stubs of pay for you. 168 00:09:08,240 --> 00:09:10,360 Speaker 1: Yeah, the stubs of paper or those things where you'd 169 00:09:10,400 --> 00:09:12,760 Speaker 1: push the thing across for the card reader. 170 00:09:12,880 --> 00:09:16,640 Speaker 2: Oh yes, yes, And that's brilliant that they still had 171 00:09:16,640 --> 00:09:18,520 Speaker 2: them and the staff knew what they were doing. I mean, 172 00:09:18,760 --> 00:09:21,720 Speaker 2: you do need these fallbacks. Hopefully we never have to 173 00:09:21,800 --> 00:09:24,000 Speaker 2: use them all very infrequently, but to have them there 174 00:09:24,080 --> 00:09:25,000 Speaker 2: is absolutely key. 175 00:09:25,440 --> 00:09:28,840 Speaker 1: Well, a cashless society is one area that's caused concern 176 00:09:28,960 --> 00:09:31,959 Speaker 1: for some. The idea of us removing physical money and 177 00:09:32,240 --> 00:09:36,360 Speaker 1: going fully digital, given some people couldn't access their accounts 178 00:09:36,440 --> 00:09:40,120 Speaker 1: or use pay systems, is that one area particularly that 179 00:09:40,280 --> 00:09:42,439 Speaker 1: might need to be re examined. 180 00:09:43,080 --> 00:09:46,240 Speaker 2: It certainly puts it at a very high risk of 181 00:09:46,480 --> 00:09:49,840 Speaker 2: the repercussions should we not be able to access that money. Obviously, 182 00:09:50,320 --> 00:09:52,120 Speaker 2: if you can't get to an ATM to withdraw the 183 00:09:52,120 --> 00:09:55,520 Speaker 2: money because the ATM's fallen over, even with cash, you're 184 00:09:55,559 --> 00:09:59,360 Speaker 2: kind of stuck. But it's definitely something to consider going 185 00:09:59,400 --> 00:10:02,240 Speaker 2: forward where everything is either on your phone or on 186 00:10:02,280 --> 00:10:02,679 Speaker 2: a card. 187 00:10:03,200 --> 00:10:07,240 Speaker 1: What's the likelihood of a global outage like this happening again, 188 00:10:07,320 --> 00:10:10,199 Speaker 1: and if so, how do we go about preventing it. 189 00:10:10,800 --> 00:10:12,920 Speaker 2: I think it's fairly likely that within the next couple 190 00:10:12,960 --> 00:10:15,959 Speaker 2: of years something similar will happen. It's just as we've 191 00:10:16,000 --> 00:10:17,920 Speaker 2: been saying that the number of providers out there is 192 00:10:17,960 --> 00:10:21,440 Speaker 2: limited in some spaces, some of them tend to monopolize 193 00:10:21,480 --> 00:10:24,480 Speaker 2: certain sexes, so it's going to hit and so it's 194 00:10:24,679 --> 00:10:27,319 Speaker 2: really having those plans and getting people to exercise them, 195 00:10:27,440 --> 00:10:29,719 Speaker 2: at the very least round a tabletop, so everyone gets 196 00:10:29,760 --> 00:10:32,160 Speaker 2: around that for a few hours and practices it, and 197 00:10:32,200 --> 00:10:34,600 Speaker 2: then every now and then actually doing a physical test 198 00:10:34,600 --> 00:10:36,920 Speaker 2: of it of knocking over a system and seeing how 199 00:10:36,960 --> 00:10:38,559 Speaker 2: you recover from it. 200 00:10:40,360 --> 00:10:42,960 Speaker 6: Microsoft's going to be looking at this closely to see 201 00:10:43,040 --> 00:10:46,400 Speaker 6: how this never happens again. From a brand perspective, they're 202 00:10:46,400 --> 00:10:49,319 Speaker 6: going to have to spend weeks and months ahead trying 203 00:10:49,360 --> 00:10:52,440 Speaker 6: to contain that. But it does speak to just a broader, 204 00:10:52,760 --> 00:10:56,160 Speaker 6: the stronger and stronger intact. We're not talking about thirty 205 00:10:56,280 --> 00:11:00,640 Speaker 6: forty companies. There's really a core ten to twenty. They're 206 00:11:00,760 --> 00:11:02,760 Speaker 6: run the global IT infrastructure. 207 00:11:05,200 --> 00:11:09,520 Speaker 1: Should we have some kind of worldwide regulatory agreement on 208 00:11:09,600 --> 00:11:10,199 Speaker 1: something like. 209 00:11:10,160 --> 00:11:14,080 Speaker 2: This, It's a very interesting idea. International regulation is absolutely 210 00:11:14,080 --> 00:11:16,000 Speaker 2: a nightmare as far as I can tell, so it 211 00:11:16,000 --> 00:11:19,000 Speaker 2: would be a good idea, But I imagine getting anything 212 00:11:19,040 --> 00:11:21,520 Speaker 2: through the United Nations or some similar body would be 213 00:11:21,600 --> 00:11:23,040 Speaker 2: very hard work in. 214 00:11:23,000 --> 00:11:27,240 Speaker 1: Terms of managing it. From a New Zealand point of view, 215 00:11:27,320 --> 00:11:31,000 Speaker 1: Is there anything our government can do to prevent something 216 00:11:31,080 --> 00:11:34,280 Speaker 1: like this happening again, or at least making it a 217 00:11:34,360 --> 00:11:37,559 Speaker 1: better turnaround, so to speak, to get everything back online. 218 00:11:37,800 --> 00:11:41,720 Speaker 2: Well, interestingly, the FMA, who regulates financial bodies, recently put 219 00:11:41,760 --> 00:11:45,040 Speaker 2: out a sort of not quite a regulation, but a 220 00:11:45,080 --> 00:11:47,920 Speaker 2: requirement that businesses actually get ready for this kind of thing, 221 00:11:48,040 --> 00:11:51,920 Speaker 2: improve their resiliency and redundancy plans. So parts of the 222 00:11:51,960 --> 00:11:55,200 Speaker 2: government are taking this seriously. What they really need to 223 00:11:55,240 --> 00:11:56,720 Speaker 2: do is kind of have a bit more of a 224 00:11:56,720 --> 00:11:58,880 Speaker 2: stick about it and go. We're going to come and 225 00:11:58,960 --> 00:12:01,720 Speaker 2: order you every year to and check these plans real 226 00:12:01,800 --> 00:12:04,640 Speaker 2: and that you've been practicing them. It should probably be 227 00:12:04,679 --> 00:12:07,440 Speaker 2: in all areas where things really matter to us, so 228 00:12:07,520 --> 00:12:11,000 Speaker 2: you know, the health, transport, financial, those kind of things 229 00:12:11,080 --> 00:12:13,640 Speaker 2: are the ones that probably need that level of plans 230 00:12:13,640 --> 00:12:14,080 Speaker 2: in place. 231 00:12:14,440 --> 00:12:17,000 Speaker 1: And in terms of the general public, should we not 232 00:12:17,640 --> 00:12:19,360 Speaker 1: get our money out of the banks and bury it 233 00:12:19,360 --> 00:12:20,079 Speaker 1: in the backyard. 234 00:12:20,480 --> 00:12:22,080 Speaker 3: I think that may be an overreaction. 235 00:12:22,600 --> 00:12:25,080 Speaker 2: I would imagine that's probably going to have as many 236 00:12:25,120 --> 00:12:27,920 Speaker 2: repercussions as doing that. But we certainly need to be 237 00:12:27,960 --> 00:12:30,559 Speaker 2: prepared ourselves, have our own sort of fire drill or 238 00:12:30,559 --> 00:12:33,640 Speaker 2: earthquake escape plan on what happens if we can't, you know, 239 00:12:33,960 --> 00:12:36,240 Speaker 2: use our card. Do we have you know, a couple 240 00:12:36,280 --> 00:12:38,760 Speaker 2: of hundred bucks in a draw that we could then 241 00:12:38,800 --> 00:12:41,600 Speaker 2: go and get groceries or whatever we need? So we 242 00:12:41,720 --> 00:12:45,480 Speaker 2: ourselves are not kind of beyond having little plans. 243 00:12:45,960 --> 00:12:47,800 Speaker 1: Yeah, a bit of a wake up call for everyone. 244 00:12:47,880 --> 00:12:50,760 Speaker 2: Hey, it is it's that complacency where we get where 245 00:12:50,800 --> 00:12:53,559 Speaker 2: it's someone else will always fix that problem. We don't 246 00:12:53,600 --> 00:12:55,480 Speaker 2: have to worry about it because it's taken care of. 247 00:12:55,840 --> 00:12:58,480 Speaker 1: Thanks for joining us, Elstair no problem, Chelsea. 248 00:12:58,559 --> 00:13:00,000 Speaker 3: It was a pleasure to talk to you. 249 00:13:04,400 --> 00:13:07,200 Speaker 1: That's it for this episode of the Front Page. You 250 00:13:07,240 --> 00:13:10,720 Speaker 1: can read more about today's stories and extensive news coverage 251 00:13:10,760 --> 00:13:14,480 Speaker 1: at enzedherld dot co dot nz. The Front Page is 252 00:13:14,520 --> 00:13:18,600 Speaker 1: produced by Ethan Siles with sound engineer Patti Fox. I'm 253 00:13:18,679 --> 00:13:22,800 Speaker 1: Chelsea Daniels. Subscribe to The Front Page on iHeartRadio or 254 00:13:22,800 --> 00:13:25,920 Speaker 1: wherever you get your podcasts, and tune in tomorrow for 255 00:13:26,000 --> 00:13:27,920 Speaker 1: another look behind the headlines.