Speaker 1: I ever feel like the Internet is well held together
Speaker 1: with like digital duct tape and hope.
Speaker 2: Yeah, I know what you mean.
Speaker 1: But today we're going deep on one of the threads
Speaker 1: that actually keeps things secure, TLS or Transport layer security.
Speaker 1: Our guide for this deep dive is TLS Mastery.
Speaker 2: Great book.
Speaker 1: It's a book that I think even if you are
Speaker 1: completely tech averse, right, you'll still find something to enjoy
Speaker 1: in this book.
Speaker 2: It's fascinating.
Speaker 1: It really makes you appreciate all that goes on that
Speaker 1: you don't even think about when you're just like behind
Speaker 1: the scenes visiting a website. Yeah, exactly. So this deep
Speaker 1: dive is your shortcut to understanding not just what TLS is,
Speaker 1: but like why you should care about it in a
Speaker 1: world that's, you know, more and more online every day.
Speaker 2: Well, and what's so interesting about TLS is it's like
Speaker 2: the security you never see at a museum. You've got
Speaker 2: your velvet ropes, maybe some security guards, but behind the scenes,
Speaker 2: there's this whole system that makes sure those priceless artifacts
Speaker 2: are protected. That's what TLS is doing.
Speaker 1: For the inner Okay, so how does TLS work its magic?
Speaker 2: Yeah?
Speaker 1: I get that it keeps data safe, but I'll admit
Speaker 1: the how has always seemed a bit.
Speaker 2: Like a magic trick.
Speaker 1: Yeah, like a magic trick to me.
Speaker 2: Well, imagine a digital fingerprint, but it's for your data. Okay,
Speaker 2: that's hashing. Okay, that's like the first line of defense.
Speaker 2: So even the tiniest change to your information, like someone's
Speaker 2: trying to, you know, sneak an extra zero onto their
Speaker 2: bank transaction, it completely alters that fingerprint, and it's going
Speaker 2: to reveal that something's been tampered with.
Speaker 1: So it's like a tamperproof seal on like my digital packages.
Speaker 2: I like that exactly.
Speaker 1: That's reassuring. But what about actually keeping the information secret
Speaker 1: like during transit? Right, That's where encryption comes in exactly. Yeah,
Speaker 1: think of it this way. Symmetric encryption is like you've
Speaker 1: got one key to a safe okay, and both you
Speaker 1: and the the recipient need that same key so super fast.
Speaker 1: But how do you share that key securely in the
Speaker 1: first place? Yeah, that seems like a bit of a
Speaker 1: chicken and egg problem.
Speaker 2: That's where asymmetric encryption saves the day. This one is
Speaker 2: more like your traditional lock and key. You've got a
Speaker 2: public key that anyone can use to send you an
Speaker 2: encrypted message, but you're the only one with the private key.
Speaker 2: You guard that closely to unlock those messages.
Speaker 1: So it's like a digital signature. Not only is the
Speaker 1: message protected, but you also know who it.
Speaker 2: Came from exactly you've got it and TLS. The really
Speaker 2: cool thing is it combines these methods. Okay, so you
Speaker 2: get the speed, you get the integrity checks, you get
Speaker 2: the secure key exchange. It's all working together, seamlessly, seamlessly
Speaker 2: behind the scenes, bind the scenes. Yeah. Magic, But here's
Speaker 2: where things get a little fuzzy for me and I'm
Speaker 2: sure for some of our listeners. How do we actually
Speaker 2: know who we're talking to online?
Speaker 1: Oh? Yeah, that's a big one. I mean, anyone can
Speaker 1: set up a website, right, anyone.
Speaker 2: Can set up a website. Yeah, So how does TLS
Speaker 2: make sure I'm not like giving my credit card info
Speaker 2: to some shady operation.
Speaker 1: You've hit on a very crucial point, and that's where
Speaker 1: digital certificates come in. Think of it like the website
Speaker 1: is showing you their ID card and it's issued.
Speaker 2: By a trusted authority called a certificate authority or CA.
Speaker 1: So it's like the Internet's passport control. To make sure
Speaker 1: that websites are who they say they are.
Speaker 2: Precisely, and just like passports, there are different levels of verification.
Speaker 1: So tell me more about these levels. What makes one
Speaker 1: digital certificate more trustworthy than another.
Speaker 2: Well, the most basic is domain validation or DV, and
Speaker 2: it simply confirms that the website owns the domain name.
Speaker 2: So it's kind of like checking that the name on
Speaker 2: the passport matches the person holding it.
Speaker 1: Right, that's a good start, but I don't know if
Speaker 1: i'd hand over like my life's savings based on that exactly.
Speaker 2: It's a good start, but not foolproof.
Speaker 1: Right.
Speaker 2: That's where organization validated or OV certificates come in. Okay,
Speaker 2: this involves a little bit more rigorous checks on the
Speaker 2: organization behind the website, so they're digging a little deeper
Speaker 2: looking at their credentials.
Speaker 1: It's kind of like they're checking those vs A stamps
Speaker 1: in the passport.
Speaker 2: Exactly where they've been, what they've been up to, are
Speaker 2: they legit? And finally, for the highest level of assurance,
Speaker 2: we've got extended validation or EV certificates. Okay, this is
Speaker 2: like the gold standard.
Speaker 1: So if a website has an EV certificate, they're basically
Speaker 1: handing me their you know, detailed personal history to prove
Speaker 1: that they're the real deal.
Speaker 2: Yes, you've got it, okay. And this whole system relies
Speaker 2: on what's called a chain of trust. Okay, So each
Speaker 2: certificate links back to the CAA that issued it, all
Speaker 2: the way up to a root CAA that's trusted by
Speaker 2: your browser.
Speaker 1: So it's like a family tree of trust exactly, ensuring
Speaker 1: that everything can be traced back to like a source
Speaker 1: that we already.
Speaker 2: Trust, Yes, a reliable source, that makes sense.
Speaker 1: But what happens when that trust is broken? Like what
Speaker 1: if a certificate gets compromised or a website you know,
Speaker 1: just goes completely rogue.
Speaker 2: That's where certificate revocation comes into play. It's like having
Speaker 2: to change the locks if a key gets stolen.
Speaker 1: Okay, So certificate revocation. Okay, So certificate revocation. It sounds
Speaker 1: crucial but kind of messy at the same time. Yeah,
Speaker 1: it's a necessary evil, right, So how does the Internet
Speaker 1: actually deal with the website going rogue? Like is there
Speaker 1: some big digital off switch.
Speaker 2: Wouldn't that be nice?
Speaker 1: Right?
Speaker 2: The reality is it's a little more complicated. Think of
Speaker 2: it like issuing a recall for a physical key. You
Speaker 2: need a way to tell everyone who might have that
Speaker 2: key that it's no longer any good.
Speaker 1: Okay, So how does that work online? Does my browser
Speaker 1: like download this massive list of revoked certificates every time
Speaker 1: I go to a new website.
Speaker 2: Well, that was one way of doing it, using something
Speaker 2: called Certificate Revocation lists or CRLs. Ok but you can
Speaker 2: imagine with today's Internet, downloading a whole phone book just
Speaker 2: to check one number is not very efficient.
Speaker 1: Yeah, that sounds about as fun as dial up. There's
Speaker 1: got to be a better way.
Speaker 2: There is. There is. It's called OCSP. It stands for
Speaker 2: Online Certificates Status Protocol okay, and it basically lets your
Speaker 2: browser do a quick check okay, in real time time
Speaker 2: to see if a specific certificate is still valid without
Speaker 2: needing that huge download.
Speaker 1: That makes a lot more sense. So okay, we've got
Speaker 1: our digital envelopes, we've got our cryptographic locks and keys.
Speaker 1: We've even got ways to like revoke access if things
Speaker 1: go sideways. But how does all this play out like
Speaker 1: in the real world? What's actually happening when I like
Speaker 1: hit enter on a website?
Speaker 2: It's a carefully choreographed dance we call the TLS handshake.
Speaker 1: Okay.
Speaker 2: So imagine you've got two secret agents meeting, okay, and
Speaker 2: they need to make sure they can trust each other. First,
Speaker 2: they're going to exchange these coded greetings, make sure they
Speaker 2: both speak TLS right. Then they're going to flash their
Speaker 2: digital certificates, you know, verify their identities.
Speaker 1: It's like checking each other's badges to make sure they're
Speaker 1: not imposters exactly exactly.
Speaker 2: Then comes the negotiation, so they agree on which version
Speaker 2: of TLS they're going to use, kind of like picking
Speaker 2: the right tools for the job.
Speaker 1: So they both make sure they're speaking the same like
Speaker 1: security language basically precisely.
Speaker 2: And then finally, once that connection is secure, they can
Speaker 2: get down to business exchange information safely and securely.
Speaker 1: That whole process sounds surprisingly fast for something so complex.
Speaker 2: It happens in the blink of an eye, but each
Speaker 2: step is crucial to making sure your data is protected.
Speaker 2: And actually TLS has this really cool trick called session resumption.
Speaker 2: Session session resumption, So imagine you go back to a
Speaker 2: website you visited recently. Okay, instead of doing that whole
Speaker 2: handshake all over again, TLS lets you reuse some of
Speaker 2: the secrets from the previous session. Oh, so the connection
Speaker 2: happens much faster.
Speaker 1: So it's like you've got a secret handshake now because
Speaker 1: speed things up with the sites that you visit all
Speaker 1: the time.
Speaker 2: Ready to go.
Speaker 1: I like that a lot. But speaking of speeding things up,
Speaker 1: let's talk about actually getting these certificates in the first place.
Speaker 1: I've heard whispers of this thing called ACME acmeme. Is
Speaker 1: it as awesome as it sounds?
Speaker 2: It is pretty great, Okay. ACME stands for Automated Certificate
Speaker 2: Management Environment Okay, and it's a game changer. Remember how
Speaker 2: we talked about certificates needed to be renewed, right ACME
Speaker 2: automates that entire process for you.
Speaker 1: So you're saying no more manually renewing certificates every few months.
Speaker 2: Ideally, not anymore.
Speaker 1: Okay, tell me more.
Speaker 2: It's basically like having a personal assistant for your website security.
Speaker 1: Okay.
Speaker 2: And the best part is it's often free and incredibly efficient.
Speaker 1: Okay. I like where this is going.
Speaker 2: ACME uses these things called challenge response mechanisms to verify
Speaker 2: that you actually own the domain.
Speaker 1: Challenge response that sounds kind of intense.
Speaker 2: It's not as intimidating as it sounds. Imagine you're trying
Speaker 2: to get into a castle okay, and you have to
Speaker 2: solve a riddle to prove you belong there okay. One
Speaker 2: of the common challenges is called HTTP zero one okay,
Speaker 2: where acme basically says, hey, I need you to put
Speaker 2: this specific file in this specific place on your server,
Speaker 2: and if it's there, boom ownership verified.
Speaker 1: So it's like leaving a sign at the castle gate
Speaker 1: to prove you actually have the.
Speaker 2: Key exactly exactly. And then there's DNS erro one, which
Speaker 2: is a little more involved. It involves creating a specific
Speaker 2: DNS record. Think of it like, I don't know, updating
Speaker 2: the castle registry with your information. A little more technical,
Speaker 2: but important for things like wild card certificates.
Speaker 1: Wild card certificates, what are those?
Speaker 2: So imagine you have one certificate that secures all the
Speaker 2: subdomains of your website. Oh wow, that's the power of
Speaker 2: wild cards.
Speaker 1: That's amazing.
Speaker 2: But like any powerful tool, you got to use it responsibily,
Speaker 2: right right.
Speaker 1: You don't want to give everyone the master key to
Speaker 1: the castle exactly exactly.
Speaker 2: It's super important when you're using acme. It's free, it's accessible.
Speaker 2: You've got to have really strong security measures in place
Speaker 2: because of that.
Speaker 1: So what kind of security measures are we talking about?
Speaker 1: What should people keep in mind?
Speaker 2: Well, one thing is rate limiting. So ACMEA providers they
Speaker 2: often have limits on how many times you can request
Speaker 2: a certificate. They don't want you going crazy, right.
Speaker 1: So don't just hit the quest certificate button a thousand
Speaker 1: times in a row exactly.
Speaker 2: For most regular users, it's not an issue, but it's
Speaker 2: just something to be aware of, especially when you're setting
Speaker 2: up your acme client.
Speaker 1: Gotcha, so pace yourself. Any other like ACME pro tips
Speaker 1: for our listeners.
Speaker 2: Yeah, always always test your ACME setup in a staging
Speaker 2: environment first.
Speaker 1: Okay.
Speaker 2: Think of it like a dress reversal before the big show,
Speaker 2: right right. You can work out all the kinks that
Speaker 2: affect in your live website.
Speaker 1: Test before you deploy golden rule. All right, So ACME
Speaker 1: sounds like a total game changer for managing certificates. But
Speaker 1: what about these other acronyms I keep hearing HSTS and CAA.
Speaker 1: Are these part of the TLS superhero team as well?
Speaker 2: Oh they are, they are, okay. HSTS stands for HTTP
Speaker 2: Strict Transport Security okay, and it's basically like putting a
Speaker 2: permanent sign on your website that says HTTPS only.
Speaker 1: Okay.
Speaker 2: Once it's enabled, it tells browsers, hey, only talk to
Speaker 2: my site over a secure connection, even if someone tries
Speaker 2: to get there through insecure HTTP.
Speaker 1: So like no more accidentally stumbling onto an insecure version
Speaker 1: of a way site.
Speaker 2: Exactly. It forces that extra level of security.
Speaker 1: I like it. What about CAA what's that all about?
Speaker 2: CIA sands for certificate authority authorization and it's like choosing
Speaker 2: which bouncers you want at the door of your website.
Speaker 1: Okay, I like that analogy a lot. So I can
Speaker 1: actually like specify which certificate authorities are even allowed to
Speaker 1: issue certificates for my domain?
Speaker 2: Yes, you got it.
Speaker 1: That's cool.
Speaker 2: It adds an extra layer of security, saying no, these
Speaker 2: are the good guys, These are the ones we trust
Speaker 2: to vouch for us.
Speaker 1: Right. If they're not on the less, they can't get in.
Speaker 2: Exactly.
Speaker 1: So HSTS and CIA you are both officially invited to
Speaker 1: my next security summit. But even with all these safeguards
Speaker 1: in place, things can still go wrong. Of course, what
Speaker 1: happens when we need to troubleshoot? You know, TLS issues
Speaker 1: are their tools for that.
Speaker 2: Absolutely, Yeah, it's always good to have a trusty toolkit
Speaker 2: for when your TLS engineers a little tune up right.
Speaker 2: One of my go tos is SSL Labs. It's online
Speaker 2: to search for it, and they have THISLSSL Configuration Tester. Okay,
Speaker 2: you literally type in your website address, it does a scan,
Speaker 2: gives you this report card the good, the bad, and
Speaker 2: the ugly of your TLS setup. I like it.
Speaker 1: No hiding from the vulnerabilities.
Speaker 2: No, not at all. And then for folks who like
Speaker 2: things a little more command line, there's tests sshole dot
Speaker 2: sh It's this really powerful script you can use to
Speaker 2: test for very specific vulnerabilities and make sure things are
Speaker 2: configured correctly.
Speaker 1: So I can use that to test different aspects of
Speaker 1: my TLS configuration and make sure everything is really buttoned
Speaker 1: up tight exactly.
Speaker 2: And then for those who really want to go down
Speaker 2: the rabbit hole, there's certificate transparency.
Speaker 1: Okay, you're going to have to elaborate on that one.
Speaker 1: What in the world I s certificate transparency?
Speaker 2: So imagine you've got this public ledger, but it's for
Speaker 2: certificates and it basically makes it much harder for these
Speaker 2: rogue certificates to slip through the cracks.
Speaker 1: Rogue certificates. Those sound kind of scary.
Speaker 2: They can be. Think of it like a fake ID,
Speaker 2: but for a website. Okay, So certificet transparency. Because it
Speaker 2: requires these certificates to be publicly logged, it makes it
Speaker 2: much easier to spot those fakes.
Speaker 1: So it's like a global neighborhood watch program exactly, but
Speaker 1: for the Internet, keeping an eye out for anything suspicious. Okay,
Speaker 1: that's reassuring. But here's a thought.
Speaker 2: You know, if we've.
Speaker 1: Got all these tools, all this technology to try to
Speaker 1: make sure that we can communicate securely online, why not
Speaker 1: just cut out the middleman and run our own WNCA.
Speaker 1: Isn't that like the ultimate control?
Speaker 2: That's an excellent question, and it's something that a lot
Speaker 2: of organizations think about, especially if they have, you know,
Speaker 2: internal networks, very specific use cases.
Speaker 1: So it's doable, but maybe not for everyone.
Speaker 2: It's doable, but it's not for the faint of heart.
Speaker 2: Let's put it that way. Okay, Running a CAA it's
Speaker 2: a big responsibility. It requires a really deep understanding of
Speaker 2: TLS cryptography security best practices. You're basically becoming your own
Speaker 2: passport office. You're issuing them, you're managing them. You have
Speaker 2: to deal with evoking them.
Speaker 1: So it's not just slapping up a website and calling
Speaker 1: it a day, No, not some serious thought that has
Speaker 1: to go into it.
Speaker 2: Definitely, you have to have certificate policies in place, key management,
Speaker 2: what are you going to do about revocation, auditing requirements.
Speaker 2: I mean, it's a whole other world.
Speaker 1: So it sounds like a fascinating world, but maybe one
Speaker 1: that's best left to the experts or people with very
Speaker 1: very specific needs, right right, But for listeners who are curious,
Speaker 1: who want to, you know, dip their toes in the
Speaker 1: CAA waters a little bit, ye, what options are out
Speaker 1: there for them? What kind of software is available if
Speaker 1: they wanted to, you know, at least understand how it
Speaker 1: works a little bit better.
Speaker 2: Well, if you're just starting out and you want to experiment,
Speaker 2: you know, in a safe environment, right, open ssl is
Speaker 2: a great option. It's free, it's incredibly powerful, It comes
Speaker 2: with everything you need to kind of set up this
Speaker 2: very basic CAA for testing, learning the ropes.
Speaker 1: That's like CAA in a box for you know, aspiring
Speaker 1: cryptographers exactly.
Speaker 2: But it's important to remember open ssl on its own,
Speaker 2: not really for production use. It's like practicing sword fighting
Speaker 2: with those you know, padded swords before you go into
Speaker 2: an actual battle.
Speaker 1: Ray, you need to get the real deal exactly.
Speaker 2: For more kind of robust, ready for the real world
Speaker 2: CAA solutions. There are other options out there, okay, and
Speaker 2: east one has, you know, its own strengths and its
Speaker 2: own quirks.
Speaker 1: So it sounds like there's a whole spectrum of CA
Speaker 1: solutions out there, from beginner friendly to something that you
Speaker 1: know an enterprise would use. Absolutely, but no matter which
Speaker 1: path you choose, it sounds like running a CA is
Speaker 1: not a decision to be made lightly.
Speaker 2: It is a responsibility.
Speaker 1: Yeah.
Speaker 2: But you know, before we get too caught up in
Speaker 2: all these kind of technical details of running a CA,
Speaker 2: let's step back for a second, right, Okay, because we're
Speaker 2: talking about certificates, we're talking about encryption. But at the
Speaker 2: heart of it, TLS is about trust, Okay. It's about
Speaker 2: making sure that the websites we visit, the information we
Speaker 2: share online, it's protected and it's legitimate trust.
Speaker 1: But verify as they say exactly.
Speaker 2: And understanding how TLS works, it gives you the power
Speaker 2: to actually make those informed decisions about your own online security.
Speaker 2: It helps you be a more discerning digital citizen.
Speaker 1: That's a really good point. It's not just about you know,
Speaker 1: blindly trusting that things are secure. It's about knowing how
Speaker 1: that security happens, right, and then demanding better protection for
Speaker 1: ourselves and our data exactly exactly.
Speaker 2: And that's something we can all strive for, regardless of
Speaker 2: our technical skill level.
Speaker 1: So we've talked about, you know, trust and how important
Speaker 1: it is in this digital world that we're living in, right,
Speaker 1: but how do we actually build that trust. Is it
Speaker 1: just about like relying on those big name certificate authorities
Speaker 1: that we see listed in our browser settings, or is
Speaker 1: there more to it than that.
Speaker 2: Well, those big names, they definitely play a crucial role, right,
Speaker 2: But it's kind of like imagine a network of trust,
Speaker 2: but it's this giant web and it spans the entire globe. Okay,
Speaker 2: so you've got your big CA's as like the central hubs,
Speaker 2: but they are all these smaller points of trust that
Speaker 2: are all interconnected.
Speaker 1: Okay, So it's not just about a few powerful entities
Speaker 1: like controlling everything. There's room for this more kind of
Speaker 1: decentralized trust to emerge exactly exactly.
Speaker 2: And we've been focusing on these publicly trusted CAAs the
Speaker 2: ones that are recognized by you know, browsers and operating
Speaker 2: systems all around.
Speaker 1: The world, right, the ones that come preinstall basically.
Speaker 2: Yeah, exactly. But what about organizations that have very specific
Speaker 2: security needs, right, or they want a bit more control
Speaker 2: over their certificate infrastructure.
Speaker 1: So you're talking about running your own private CAA. We
Speaker 1: touched on it a little earlier. Yes, but it sounded
Speaker 1: kind of intense.
Speaker 2: It can be. It can be, but it's also not
Speaker 2: as daunting as it might seem. Okay, think of it
Speaker 2: like you're creating this little circle of trust. Okay, but
Speaker 2: it's within your organization, right. You set the rules, you
Speaker 2: manage the keys. You have total control over who gets
Speaker 2: certificates and what they're allowed to do with them.
Speaker 1: So it's like a self governed digital nation, yes, issuing
Speaker 1: their own passports and visas exactly, Okay, And.
Speaker 2: This is really popular for things like you know, internal networks,
Speaker 2: where you might have devices or applications that need to
Speaker 2: be able to talk to each other securely, but they
Speaker 2: don't need to be publicly trusted. Yeah.
Speaker 1: Right, It's like their own little private check room that
Speaker 1: nobody else has access to.
Speaker 2: There you go, and what's cool is you can tailor
Speaker 2: these private CAAs to your specific needs. Right, you set
Speaker 2: the rules, you determine how high you want the bar
Speaker 2: for security, and you have complete control over your data.
Speaker 1: That's very cool, But I do imagine there are some
Speaker 1: challenges that come with that.
Speaker 2: Right of course, running a private CAA, even if it's
Speaker 2: a small one, it's a big responsibility.
Speaker 1: Right.
Speaker 2: You need to have plans for key management, certificate revocation,
Speaker 2: what happens if something goes really wrong, like disaster recovery,
Speaker 2: Because if your CAA goes down, that could really disrupt
Speaker 2: your organization's ability to communicate securely.
Speaker 1: So it's not just like set it and forget it, No,
Speaker 1: not at all. Up keep involved. There's maintenance.
Speaker 2: Absolutely, I stay vigilant. But for folks who are willing
Speaker 2: to put in the time and effort, running a private
Speaker 2: CAA can give you a level of security and control
Speaker 2: that you just don't get with the publicly trusted ones.
Speaker 1: It's like you're building your own fortress brick by digital brick.
Speaker 1: So we've covered a lot today. We went from these
Speaker 1: like fundamental concepts of TLS all the way to these
Speaker 1: you know what seems like very complex setting up your
Speaker 1: own CA. Right, it seems like online trust is this
Speaker 1: like very multi layered thing that's constantly evolving. Absolutely, So,
Speaker 1: as our listeners kind of go forth from this deep dive,
Speaker 1: what are your I don't know, final parting thoughts? Words
Speaker 1: of wisdom for them as they navigate this digital world.
Speaker 2: I think the most important takeaway from all of this is, Yeah,
Speaker 2: knowledge is power. The more you understand how TLS works,
Speaker 2: the better equipped you are to protect yourself online. Don't
Speaker 2: be afraid to ask questions, you know, do your research,
Speaker 2: demand a better security from the websites you visit, in
Speaker 2: the companies that you trust with your data.
Speaker 1: Absolutely, don't just blindly trust that little lock icon in
Speaker 1: your browser, right exactly? Like what does it represent and
Speaker 1: what did it take for that website to earn that
Speaker 1: you know, little badge of honor?
Speaker 2: Exactly? And I think the more we all understand about
Speaker 2: this stuff, the more we can push for a better
Speaker 2: internet for everybody.
Speaker 1: Well said, Well said, A huge thank you to our
Speaker 1: expert for you know, really demystifying this world of TLS
Speaker 1: and CAS. It's a lot to take in, but hopefully
Speaker 1: everybody feels a little bit more empowered. Absolutely, and to
Speaker 1: our listeners, Thank you as always for joining us on
Speaker 1: this deep dive, and remember the journey to a more
Speaker 1: secure online experience, it all starts with a single step,
Speaker 1: or maybe, in this case, like a click on that
Speaker 1: learn more button. Until next time, stay curious, stay informed,
Speaker 1: and stay secure.