> For the complete documentation index, see [llms.txt](https://docs.talsec.app/appsec-articles/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talsec.app/appsec-articles/articles/talsec-presentable-demo-showcase-of-talsec-technologies.md). # Talsec Presentable Demo: Showcase of Talsec technologies Talsec provides many security solutions, providing security to millions of users around the world. However, security as a whole often feels very abstract and difficult to understand. If you're the kind of person who learns by doing, we have a demo app for you. Presentable Demo is an all-in-one playground that shows Talsec's capabilities: [RASP+](https://docs.talsec.app/premium-products/product/rasp), [AppiCrypt®](https://docs.talsec.app/premium-products/product/appicrypt), [Malware Detection](https://docs.talsec.app/premium-products/product/malware-detection), Device Risk State and Integration within [Talsec Portal](https://my.talsec.app). ## Get it now There are two ways how to test Demo, depending on how hands-on you want to be. **Live, walked by an engineer:** {% hint style="success" %} You can plan the live meeting with our experts [**here**](https://crm.talsec.app/request-a-free-demo). {% endhint %} **Self-assessment:**\ Prefer to click around on your own? You can request access through the Talsec team. You can then install provided APK on your own device and walk it on your own pace. {% hint style="success" %} You can fill form for self-assement [**here**](https://4me5v.share.hsforms.com/2xyawex8YTsaFcbkDnqkXPA). {% endhint %} ## Who is it for?


Security & Security Engineers	For evaluating SDK capabilities.
Mobile leads & SecOps	For assessing the dashboard/analytics experience.
Partner & alliance managers	For crisp, repeatable demo narrative that covers the whole platform.

## RASP+ First line of defense against threats. [RASP+](https://docs.talsec.app/premium-products/product/rasp) (Runtime Application Self-Protection) is based on checks that run inside the app while it's live, watching for signs the environment has been tampered with. Typical checks include a root or jailbroken OS, a debugger attached, a hooking framework like Frida, an emulator, or a repackaged build.

Demo app runs full set of security checks and detections including: * Root/Jailbreak detection * Hooking detection * App Integrity detection * Emulator/Simulator detection * Debugger detection * and much more In the demo, you'll see these fire in real time as you trigger them. {% hint style="info" %} Easiest check to trigger is screenshot. Try taking screenshot while demo app is open. {% endhint %} ## Device Risk State RASP+ tells the app what's happening on the device right now. **Device Risk State** turns those live signals into a single verdict - a risk score, plus the threat report behind it. Based on those, you can act on the overall trustworthiness of the session. It's designed for a seamless security step-up during sensitive moments such as: * Entering a payment * Confirming a transfer * Accessing sensitive data In those cases a compromised device shouldn't be allowed to proceed.

In the demo you can open the current session's Risk State report and see it broken down: * Risk score * Findings * Device posture * Threat evidence ## Protect API Detecting a threat on the device is only half the job. Your backend still has to decide, for every request, whether the client it's talking to can be trusted - and it can't take the app's word for it. RASP is strong on its own, but an attacker might still bypass its reactions and strip away part of the protection. ### AppiCrypt® [AppiCrypt®](https://docs.talsec.app/premium-products/product/appicrypt) (and [AppiCrypt for Web](https://docs.talsec.app/premium-products/product/appicryptweb)) serves as second line of defense against threats, primarily protecting API which app makes call to. The SDK generates a unique token (cryptogram) to each API call allowing you to implement transaction signing for every request. Cryptogram is a one-time cryptographic proof, bound to the request, that carries the app and device integrity state with it. It's strictly point-to-point connection between your app and your endpoint, no third party server or service is involved. Cryptogram is verified by small script on your backend. If verification fails the call gets rejected before it hits your business logic. Since the cryptogram is per-call and not tied to a validity window, a stolen one is useless.

The demo visualizes this process end-to-end: 1. Cryptogram verification 2. Attaching cryptogram to header and sending request 3. Parsing and evaluating cryptogram ## Protect User A device is only as trustworthy as the other apps sharing it. Even a perfectly healthy app can be undermined by malware sitting right next to it which is using techniques like: * Reading the screen * Intercepting SMS * Overlaying your UI ### Malware Detection The third line of defense is [malware detection](https://docs.talsec.app/premium-products/product/malware-detection). It is an active in-app protection against known and zero-day malware, ongoing campaigns, counterfeit app clones, and other risky apps that could compromise user data or your backend. A device carrying suspicious apps can itself be considered unsafe. It works in two complementary modes: * **On-device offline scanning** needs no network - it uses package blocklists, permission-based risk assessment, and behavioral heuristics, catching threats that hash-based databases miss because malware permutes its hash so easily. * **Optional online reputation check** then confirms findings against a live malware database powered by [Gen (Norton, Avira, Avast)](/appsec-articles/articles/how-our-partnership-with-gen-digital-enabled-malware-detection-v2-powered-by-avast-and-norton-dbs.md) and drawn from 500 million users worldwide, letting you balance privacy, performance, and coverage to your own risk model.

## Insights about threats Collected threats are visualized in the [**Talsec Portal**](https://my.talsec.app)**.** It the centralized dashboard where your app's security intelligence lives, giving you real-time insight into threats, incidents, and how you compare to the rest of the market. It breaks the signals down into graphs: It breaks down in graphs: * incident rate over time * breakdown of privileged-access (root/jailbreak) events * app-integrity * reverse-engineering attempts * mix of environments the app ran in. Trigger something in the demo app, and it turns up here.

## Disclaimers **Scope of demo**\ This demo shows what the protections detect and how they surface, not a full security assessment of your app. This demo is not for a penetration testing purposes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talsec.app/appsec-articles/articles/talsec-presentable-demo-showcase-of-talsec-technologies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.