What does it look like for, or what, how difficult is it, what should developers keep in mind if the AppSec team comes and says, "We need to secure our mobile app"? Which I understand is pretty generic and probably over-broad, but help me make that more granular and more actionable for, for that developer team.

Yeah.

Yeah, I think the, the answer is in having these different layers that can complement each other and work together in, in protecting your application.

And then, you know, an area that we've spent a lot of time researching and focusing in on is, um, this concept of really applying it at the compiler level to the applications that we're protecting.

Um, so there's different strategies for how you can protect an application.

Some strategies would be to encrypt the application itself and have some startup code and whatnot that, um, decrypts the application while it's running, and that works well, but that's, that's what we would characterize as a single layer of app protection.

So it's encrypted, which is great, except that that encryption key is obfuscated somewhere in that startup logic, and if you manage to manipulate that, you've now got a way to bypass that protection, uh, layer.

Are there things there that could, that the OS itself could do that would help mobile developers, you know, have, have better attestation, better confidence, better trust, or is this very much the responsibility of the, the mobile app itself?

Or what, how difficult is it? What should developers keep in mind if the AppSec team comes and says, "We need to secure our mobile app," which I understand is pretty generic and probably over-broad, but help me make that more granular and more actionable for, for that developer team.

Yeah.

Yeah, I think the, the answer is in having these different layers that can complement each other and work together in, in protecting your application.

And then, you know, an area that we've spent a lot of time researching and focusing in on is, um, this concept of really applying it at the compiler level to the applications that we're protecting.

Um, so there's different strategies for how you can protect an application.

Some strategies would be to encrypt the application itself and have some startup code and whatnot that, um, decrypts the application while it's running, and that works well, but that's, that's what we would characterize as a single layer of app protection.

So it's encrypted, which is great, except that that encryption key is obfuscated somewhere in that startup logic.

Are there things there that could, that the OS itself could do that would help mobile developers, you know, have, have better attestation, better confidence, better trust, or is this very much the responsibility of the, the mobile app itself?

What does it look like for, how difficult is it? What should developers keep in mind if the AppSec team comes and says, we need to secure our mobile app, which I understand is pretty generic and probably overbroad, but help me make that more granular and more actionable for that developer team.

Yeah, I think the answer is in having these different layers that can complement each other and work together in protecting your application.

And then an area that we've spent a lot of time researching and focusing in on is this concept of really applying it at the compiler level to the applications that we're protecting.

So there's different strategies for how you can protect an application.

Some strategies would be to encrypt the application itself and have some startup code and whatnot that decrypts the application while it's running.

And that works well, but that's what we would characterize as a single layer of app protection.

So it's encrypted, which is great, except that that encryption key is obfuscated somewhere in that startup logic.

Are there things there that the OS itself could do that would help mobile developers have better attestation, better confidence, better trust? Or is this very much the responsibility of the mobile app itself?

What does it look like for, how difficult is it? What should developers keep in mind if the AppSec team comes and says, we need to secure our mobile app, which I understand is pretty generic and probably overbroad, but help me make that more granular and more actionable for that developer team.

Yeah, I think the answer is in having these different layers that can complement each other and work together in protecting your application.

And then an area that we've spent a lot of time researching and focusing in on is this concept of really applying it at the compiler level to the applications that we're protecting.

So there's different strategies for how you can protect an application.

Some strategies would be to encrypt the application itself and have some startup code and whatnot that decrypts the application while it's running.

And that works well, but that's what we would characterize as a single layer of app protection.

So it's encrypted, which is great.

Are there things there that the OS itself could do that would help mobile developers have better attestation, better confidence, better trust? Or is this very much the responsibility of the mobile app itself?

So fill us in.

Yeah, so I'm a 27-year Army veteran, and like a lot of veterans, the Star-Spangled Banner is near and dear to my heart.

And having deployed to Iraq a couple times, I can tell you that Uh, I've probably been moved to tears by the national anthem more than most adults, but there's something special about the fourth verse of the national anthem that is, is not really conveyed by what we normally hear out there with, you know, just the first verse.

Um, it talks about, you know, the first verse talks about American resilience and, uh, you know, it sets the, the tone for that, uh, Battle of Fort McHenry.

And the fourth verse, though, really conveys the why behind it.

So the Why We Stand project that I'm starting is to... convey that really deep why, and it conveys American exceptionalism and, you know, providential, you know, support of the United States that I don't think you get from verse one.

Ryan, how can people find out more about this and become part of this?

So I do have a Facebook page called the Why We Stand Project, and you can find it on Instagram, too.