‫However, we can't always encrypt we found out, guys, why, because sometimes I need to perform operation
‫on the on the data and it's new that it needs to be plain text.
‫You cannot, for example, perform database quiz on encrypted data.
‫You cannot do select star from Blair where where ID equals seven.
‫Well, the seven, the data is encrypted.
‫So how do you do that?
‫The only way is to actually either have it plaintext unencrypted stored on disk, which is pretty much
‫what we do today or have the database store it encrypted, but when we want it perform, then the queries
‫we decrypt the data using the key and then we have to do with deal with the key management and stuff
‫like that, which is another hassle.
‫Right.
‫And then turn out an encrypted again.
‫So that's where we where we can do today that there is no solution.
‫That's what we do.
‫Twitter, same thing.
‫They cannot encrypt their data.
‫Nobody encrypt their data in the database today.
‫Right.
‫Why?
‫Because not only that, they want to run trends.
‫Right.
‫Twitter want to run trends.
‫They want to run their analytics.
‫They want to compute a recommendation.
‫They can't keep the encrypting on the back backend.
‫They cannot do that all the time.
‫Maybe you can, but it's it's always there was there will be an agent that decrypt at the end of the
‫day and the agent that decrypts, if you don't trust it, tough luck analysis, indexing, database
‫tuning can do any of that.
‫Has to be unencrypted.
‫Right.
‫Tough luck.
‫Right.
‫Applications must read the data in order to process it.
‫Right.
‫Even if the data is encrypted on disk and you read it encrypted.
‫Right.
‫So whoever snoops in the network cannot really read it.
‫But the moment the reach is you as an agent, as an as an application, as a backend application, as
‫a Web server, as xpress, as no jass, as python jangle, you got to decrypt it in order to make sense
‫of it.
‫Right.
‫And once you do that, it's available.
‫Right.
‫And the question is, do you trust this application or not?
‫Not.
‫So same thing.
‫We have this concept of trust termination on layer seven, reverse proxies and load balancers.
‫Right.
‫All load balancers that that act of the layer seven, if the traffic is encrypted with a steeps, it
‫has to say stop.
‫I need to look at the data.
‫What what does it do?
‫It terminates deals.
‫What does that mean?
‫It means it serves the load balancer certificate to the client and decrypt all the traffic.
‫Looks at the data, look at the records, look at the post.
‫Of course, look at the path.
‫And then based on that, execute rules that you have put on the application.
‫So I can know your horse, I can know where you're going, I can know the path, and I can execute micro
‫services logic.
‫Right.
‫So if you're going slash pictures, then I'm going to take you to this set of back end servers.
‫If you're going to slash comments, I'm going to take you to this back end servers.
‫You cannot do this if you can.
‫If you don't decrypt today, we decrypt DNS termination and reverse proxies.
‫Apparently they brag about the features.
‫That way we do Telus termination.
‫We're good.
‫Well, it is official.
‫All right.
‫But you're up the traffic.
‫And although a lot of people against this concept, Steve Gibson is one of them.
‫And we're going to reference the video below us.
‫I'm not gonna give you a reverse proxy or not seven bucks the audience protector to to look at my traffic
‫just to do your operations.
‫No, sir.
‫I'm not going to give you my private and certificate to serve it.
‫He's just not comfortable with it.
‫And so many other people are not comfortable with Layer seven reverse proxies.
‫Right.
‫That's the nature of the beast, I guess.
‫Right.
‫But that's why people prefer layer four load balancers where it will stream all the way to the back
‫end.
‫Well, it has it's efficient.
‫It's not as efficient as layer seven.
‫OK, you cannot do Poulenc cannot do all the stuff.
‫But that's a big, big, big problem in that in the back engineering community today, tearless termination.