Tampering Events
Focus
Focus
Prisma Browser

Tampering Events

Table of Contents

Tampering Events

Tampering events are generated when Prisma Browser detects unauthorized modifications to its files, processes, network communications, or engine integrity.

Event Types

Event TypeUI NameDescription
fileTamperingFile tamperingBrowser files were modified outside of the normal update process
talonEngineTamperingEngine tamperingPrisma Browser security engine was tampered with
processTamperingProcess tamperingAn unauthorized process attached to or modified the browser process
networkTamperingNetwork tamperingBrowser network communications were intercepted or modified
pbInfraNetworkTamperingInfra network tamperingPrisma Browser infrastructure communications were tampered with
mobileAppTamperingMobile app tamperingPrisma Browser mobile application integrity was compromised
rceExploitAttemptRCE exploit attemptA remote code execution exploit was detected and blocked

Context Fields

FieldUI LabelDescription
tampering.typeDescriptionThe specific type of tampering detected

Tampering Types — Desktop (Windows/macOS)

The tampering.type field provides detailed information about what was detected:
Tampering TypeDescription
Browser binary modifiedPrisma Browser executable was modified after installation
Internal file modifiedAn internal browser file was modified outside the update process
Debugger attachedA debugger was attached to the browser process
Restricted CLI args usedThe browser was launched with restricted command-line arguments

Tampering Types — Network / Infrastructure

Tampering TypeDescription
Invalid Talon infrastructure certificateAn invalid TLS certificate was detected on infrastructure communication
Invalid trust store certificateThe browser trust store was modified with an unauthorized certificate
Talon infrastructure message changedA message in the infrastructure communication channel was altered

Tampering Types — Mobile (Android/iOS)

Tampering TypeDescription
Frida detectedThe Frida dynamic instrumentation toolkit was detected on the device
Emulator detectedThe application is running in an emulator rather than a real device
Unknown installerThe application was installed from an unknown/untrusted source
App not installedThe application integrity check found the app is not properly installed
App UID mismatchThe application user ID does not match expected values
Cloud project number is invalidThe Firebase/GCP project number is invalid
Request hash too longThe integrity attestation request hash exceeds allowed length
Expired tokenThe integrity attestation token has expired
Invalid tokenThe integrity attestation token is invalid
Invalid package nameThe application package name does not match expected values
Forbidden package nameThe application package name is on the forbidden list
Invalid request hashThe integrity request hash is invalid
Invalid request timestampThe integrity request timestamp is outside the valid window
Invalid app recognition verdictThe Play Integrity app recognition verdict indicates tampering
Empty device recognition verdictThe device integrity check returned no verdict
Invalid device recognition verdictThe device failed integrity verification
Invalid app licensing verdictThe app licensing verification failed

Process Context

When available, process information is included with tampering events:
FieldUI LabelDescription
process.pidProcess IDThe process identifier
process.imagePathProcess image pathThe full path to the process executable
process.cliArgsProcess Command-Line argumentsThe command-line arguments used to launch the process
process.parentProcess.imagePathParent process pathThe parent process executable path

Certificate Context

For network and infrastructure tampering events involving certificates:
FieldUI LabelDescription
certificate.issuerCertificate issuerThe certificate issuer name
certificate.subjectCertificate subjectThe certificate subject name
certificate.serialNumberSerial numberThe certificate serial number
certificate.createdTimeCreatedCertificate creation timestamp
certificate.expirationTimeExpirationCertificate expiration timestamp
certificate.fingerprints[].valueFingerprintCertificate fingerprint hash value
certificate.fingerprints[].algorithmAlgorithmHash algorithm used (MD5, SHA-1, SHA-256, SHA-512)

RCE Exploit Context

The rceExploitAttempt event is generated when the browser detects an attempted remote code execution exploit (e.g., via WebAssembly-based attacks):
FieldUI LabelDescription
rceExploit.sensorDetection SensorThe sensor that detected the exploit (e.g., WASM_GUARD)
rceExploit.urlExploited URLThe URL where the exploit was attempted

Examples

File Tampering — Browser Binary Modified
FieldValue
TypeFile tampering
CategoryTampering
Userunknown.user@acme.com
Tampering typeBrowser binary modified
Process ID4521
Process image pathC:\Program Files\Prisma Browser\browser.exe
ActionBlocked
SeverityVery high
OSWindows 11
Process Tampering — Debugger Attached
FieldValue
TypeProcess tampering
CategoryTampering
Userdev.engineer@acme.com
Tampering typeDebugger attached
Process ID8892
Process CLI arguments--remote-debugging-port=9222
ActionBlocked
SeverityVery high
Network Tampering — Invalid Infrastructure Certificate
FieldValue
TypeInfra network tampering
CategoryTampering
Userjane.doe@acme.com
Tampering typeInvalid Talon infrastructure certificate
Certificate issuerCN=Unknown CA
Certificate subjectCN=*.prisma-browser-infra.com
ActionBlocked
SeverityVery high
Mobile App Tampering — Frida Detected
FieldValue
TypeMobile app tampering
CategoryTampering
Usermobile.tester@acme.com
Tampering typeFrida detected
ActionBlocked
SeverityVery high
DevicePIXEL-7-PRO
OSAndroid 14
RCE Exploit Attempt
FieldValue
TypeRCE exploit attempt
CategoryTampering
Userbob.jones@acme.com
Exploited URLwww.compromised-blog.net/article/malicious
Detection SensorWASM_GUARD
ActionBlocked
SeverityVery high
OSWindows 11