# Guardsquare Blog Our blog home page. Here you can learn more about Guardsquare, our products and mobile application security. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Safeguarding LLM-Assisted Dev at Guardsquare | Guardsquare DevFeed: [Safeguarding LLM-Assisted Dev at Guardsquare | Guardsquare]() Original publisher: [Read original article]() Author: Noah Fraiture - Backend Engineer Published: 2026-09-15T13:03:38Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Development](), [Large Language Model](), [Cybersecurity](), [Security & Privacy](), [agent observability]() Tags: [ai-agents](), [android](), [containers](), [cybersecurity](), [data](), [dev](), [developer](), [development](), [ios](), [llm](), [llm-gateway](), [thought-leadership]() ### AI overview Guardsquare explains why it adopted LLM-assisted software development despite risks involving sensitive intellectual property, personally identifiable information, and agent access to developer infrastructure. The post describes safeguards including separating sensitive code, isolating agent execution, and controlling model access and outbound data through an LLM gateway and guardrail service. ### Source excerpt This post is not meant to tell you how to use large language models (LLMs) or to claim we've found the right approach. As a cybersecurity company working with particularly sensitive IP, our decision to use LLMs for development was never just about productivity. The broader enthusiasm around LLMs was not itself a reason for us to adopt them quickly. For some time, our position was that the risks outweighed the productivity gains, and incidents involving AI agents elsewhere in the industry reinforced that assessment. ## How to Deprecate Old Mobile App Versions for Security DevFeed: [How to Deprecate Old Mobile App Versions for Security]() Original publisher: [Read original article]() Author: Anton Baranenko - Product manager Published: 2026-09-08T12:25:47Z Content type: tutorial Language: en Sources: [Guardsquare Blog]() Topics: [Mobile](), [Security](), [App](), [SDKs]() Tags: [android](), [app](), [app-attestation](), [dexguard](), [ios](), [ixguard](), [mobile](), [sdk](), [security]() ### AI overview This article examines how to deprecate old mobile app versions after a security vulnerability is fixed. It explains why removing vulnerable versions from official app stores is insufficient and evaluates update mechanisms, including platform-provided in-app updates, from a security perspective. ### Source excerpt Here's a security incident scenario. You ship a mobile app with insufficient tampering protection, and someone finds it. Now the app can be modified and repackaged into a malicious version with almost no effort. ## MAST in the Age of Open Source Software |Guardsquare DevFeed: [MAST in the Age of Open Source Software |Guardsquare]() Original publisher: [Read original article]() Author: Simon Haven - Product Marketing Manager Published: 2026-09-01T10:59:01Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Open Source](), [Mobile Security](), [Application Security](), [Vulnerabilities](), [Social engineering](), [npm]() Tags: [app-security-testing](), [application-security](), [appsweep](), [general](), [malware](), [mobile](), [mobile-apps](), [npm](), [open-source](), [open-source-software](), [social-engineering](), [supply-chain](), [vulnerabilities]() ### AI overview This article explains why mobile application security testing is important when apps use free and open source software. It describes how vulnerable, deprecated, compromised, and transitive third-party dependencies can expand an app's attack surface, citing a September 2025 npm supply chain attack as an example. ### Source excerpt Building with free and open source software (FOSS) has become common practice for app developers. In 2022, it was estimated that between 70% and 90% of any given software codebase was made up of open source components. Leveraging open source projects presents many advantages: ## What is Mobile App Reverse Engineering? | Guardsquare DevFeed: [What is Mobile App Reverse Engineering? | Guardsquare]() Original publisher: [Read original article]() Author: Guardsquare Published: 2026-08-25T10:43:34Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Reverse Engineering](), [Mobile Security](), [Mobile](), [Security](), [Ghidra](), [Hopper]() Tags: [analysis](), [android](), [dexguard](), [ios](), [ixguard](), [mobile](), [reverse-engineering](), [security](), [thought-leadership](), [tools](), [vulnerabilities]() ### AI overview The article explains mobile app reverse engineering as the analysis of compiled binaries to reconstruct an app's logic, data flows, and structure. It describes legitimate diagnostic uses, attacker risks such as credential extraction and vulnerability discovery, why iOS and Android protections do not fully protect application code, and static analysis using tools including Ghidra and Hopper. ### Source excerpt Reverse engineering is the process of analyzing compiled software to understand how it works, without having access to the original source code. In the context of mobile applications, it means taking a published app and working backward through its binary to reconstruct its internal logic, data flows, and structure. ## Modern App Protection Requires Polymorphism | Guardsquare DevFeed: [Modern App Protection Requires Polymorphism | Guardsquare]() Original publisher: [Read original article]() Author: Jason Cortlund - Technical Marketing Writer Published: 2026-08-18T13:45:43Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Mobile](), [Mobile Security](), [Polymorphism](), [Security](), [Development](), [Artificial Intelligence](), [Large Language Model]() Tags: [agentic-ai](), [ai](), [development](), [dexguard](), [ixguard](), [large-language-models-llms](), [mobile](), [polymorphism](), [protection](), [reverse-engineering](), [security](), [security-research](), [thought-leadership](), [vulnerabilities]() ### AI overview The article argues that mobile app protection should use polymorphism, with protections changing for each application build. It links this approach to the risks created by development speed, AI-generated code, and scalable reverse-engineering attacks. ### Source excerpt According to credit reporting agency Equifax, "...mobile app security is often neglected by developers -- making apps more vulnerable to fraud." The reason for this is quite simple for most organizations: development speed is the dominant priority. In fact, 79% of mobile developers cite time-to-market pressure as the top barrier to stronger protection. ## How Mobile App Security from Guardsquare Addresses Gaps in Framework Compliance DevFeed: [How Mobile App Security from Guardsquare Addresses Gaps in Framework Compliance]() Original publisher: [Read original article]() Author: Guest post by Dr. Edward Amoroso, CEO, TAG Infosphere Inc. and former AT&T Chief Security Officer Published: 2026-08-11T14:00:31Z Content type: opinion Language: en Sources: [Guardsquare Blog]() Topics: [Mobile Security](), [Application Security](), [Security](), [Cybersecurity](), [Artificial Intelligence]() Tags: [application-security](), [compliance](), [credentials](), [cybersecurity](), [frameworks](), [governance](), [hardening](), [mobile](), [protection](), [regulatory](), [report](), [security](), [standards]() ### AI overview A featured guest post examines how mobile application security, including Guardsquare's hardening, runtime protection, and anti-tampering capabilities, can help enterprises address gaps in compliance frameworks. It also argues that frameworks such as NIST CSF 2.0 should more explicitly account for mobile app risk. ### Source excerpt Former AT&T Chief Security Officer and TAG Infosphere founder Dr. Edward Amoroso shares his perspective on the state of mobile application security in a featured guest post for Guardsquare. Enterprise compliance is evolving as organizations face mounting regulatory pressure and more capable threat actors. Regulators now expect alignment to frameworks such as National Institute of Standards and Technology Cybersecurity Framework (CSF) 2.0 and sector-specific mandates. Yet, while governance has matured around cloud, endpoint, and networks, mobile app risk remains underrepresented in compliance frameworks and control processes. ## Rethinking Mobile App Security | Guardsquare DevFeed: [Rethinking Mobile App Security | Guardsquare]() Original publisher: [Read original article]() Author: Guardsquare Published: 2026-08-04T13:02:55Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Mobile Security](), [Security](), [Testing](), [Development]() Tags: [android](), [development](), [ios](), [mobile](), [mobile-security](), [process](), [protection](), [security](), [testing](), [thought-leadership](), [vulnerabilities]() ### AI overview The article argues that mobile app security failures span code, development, testing, APIs, and production rather than occurring in one isolated place. It recommends integrating continuous security testing into the development lifecycle and protecting application logic such as payment flows, authentication mechanisms, and proprietary algorithms. ### Source excerpt Mobile app security rarely breaks in a single place. Instead, it fails across layers that were never designed to work together. ## The Hidden Costs of DIY Android App Security | Guardsquare DevFeed: [The Hidden Costs of DIY Android App Security | Guardsquare]() Original publisher: [Read original article]() Author: Michael Olechna - Product Marketing Manager Published: 2026-07-28T13:00:55Z Content type: opinion Language: en Sources: [Guardsquare Blog]() Topics: [Security](), [Android](), [Mobile](), [obfuscation](), [R8](), [Open Source]() Tags: [android](), [dexguard](), [mobile](), [obfuscation](), [open-source](), [protection](), [r8](), [security](), [thought-leadership](), [threat-monitoring]() ### AI overview The article argues that DIY Android app security built around open-source tools can leave important protection gaps. It explains that R8 helps compile and optimize Android applications but is not a complete security solution, lacking capabilities such as string encryption, API endpoint security, and control-flow obfuscation. ### Source excerpt The DIY temptation to build with open-source is strong for mobile app developers. After all, their job is to build, secure, and design new applications, features, and architectures that benefit the users of their apps. ## Mobile App Security Without Sacrificing UX | Guardsquare DevFeed: [Mobile App Security Without Sacrificing UX | Guardsquare]() Original publisher: [Read original article]() Author: Ryan Lloyd - Chief Product Officer Published: 2026-07-21T13:02:06Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Mobile Security](), [Application Security](), [Security](), [obfuscation](), [User experience (UX)](), [Reverse Engineering](), [Jailbreak](), [debug]() Tags: [application-security](), [jailbreak](), [mobile](), [obfuscation](), [performance](), [profiling](), [reverse-engineering](), [security](), [technical](), [time](), [ux]() ### AI overview The article explains how profiling instrumented mobile applications helps teams apply obfuscation and runtime security controls at appropriate levels while limiting effects on stability, performance, and user experience. It also discusses automating application profiling at scale through AI-driven and agentic testing. ### Source excerpt Mobile application security has evolved significantly over the past decade. Modern applications routinely employ code obfuscation, runtime application self-protection (RASP), anti-tampering controls, jailbreak and root detection, debugger detection, certificate pinning, and a variety of other runtime defenses designed to protect intellectual property and sensitive user data. ## Why OS-Level Security Isn't Enough for Mobile Apps | Guardsquare DevFeed: [Why OS-Level Security Isn't Enough for Mobile Apps | Guardsquare]() Original publisher: [Read original article]() Author: Simon Haven - Product Marketing Manager Published: 2026-07-14T12:36:57Z Content type: opinion Language: en Sources: [Guardsquare Blog]() Topics: [Mobile Security](), [Application Security](), [Security](), [Android](), [iOS](), [Reverse Engineering]() Tags: [android](), [application-security](), [attacks](), [dexguard](), [general](), [ios](), [ixguard](), [mobile-security](), [os](), [reverse-engineering](), [security]() ### AI overview The article argues that Android and iOS security protections primarily protect devices and users, but do not comprehensively verify whether mobile application code remains trustworthy after deployment. It recommends dedicated mobile application security alongside operating-system protections to reduce risks such as reverse engineering and runtime tampering. ### Source excerpt Since day one, Google and Apple have integrated security features into their respective operating systems, Android and iOS. However, as mobile devices have grown to become near ubiquitous, so, too, have the attacks targeting them. In 2025, 43% of surveyed organizations cited mobile app threats as a top contributor to mobile security breaches, according to a report by Verizon. In response, Google and Apple have continued introducing stronger and more refined security tools and features with each new release. ## Mobile App Security in the Age of SoftPOS | Guardsquare DevFeed: [Mobile App Security in the Age of SoftPOS | Guardsquare]() Original publisher: [Read original article]() Author: Guardsquare Published: 2026-07-07T11:42:02Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Mobile](), [Mobile Security](), [Security](), [App](), [API](), [Exploit](), [SDKs](), [Malware]() Tags: [android](), [api](), [compliance](), [credentials](), [devices](), [exploit](), [financial-services](), [integrity](), [ios](), [malware](), [mobile](), [payment](), [payments](), [pos](), [protection](), [sdks](), [security](), [smartphone](), [thought-leadership]() ### AI overview This article examines the security implications of SoftPOS, which turns smartphones into card-present payment terminals. It explains that moving payment functions to mobile devices shifts responsibility to the device, operating system, application integrity, APIs, and runtime environment, and discusses threats including app tampering, reverse engineering, API abuse, credential theft, malware, and bypassed environment checks. ### Source excerpt As retailers look for faster, more flexible ways to accept payments, SoftPOS is becoming a cornerstone of modern payment strategies. It's expected that by 2027, more than 34.5 million merchants will accept payments through SoftPOS technology. The ability to turn any smartphone into a card-present terminal reduces hardware costs, simplifies onboarding, and supports new use cases like curbside, pop-up stores, and in-aisle checkout.