Online Help Center Home
Privacy and Personal Data Collection Disclosure
- Pre-release Disclaimer
- Pre-release Sub-feature Disclaimer
Trend Vision One Data Privacy, Security, and Compliance
What's New
- May 2023
- April 2023
- March 2023
Introduction
- Trend Vision One
- Checking the Trend Vision One Service Status
  - SERVICE LEVEL OBJECTIVES FOR TREND VISION ONE (herein this “SLO”)
Getting Started
- Getting Started with Trend Vision One
- Getting Started with Vulnerability Prioritization and Assessment
Risk Insights
- Executive Dashboard
- Attack Surface Discovery
- Operations Dashboard
- Security Dashboard
  - Customizing the Security Dashboard
- Report Management
XDR Threat Investigation
- Detection Model Management
- Workbench
  - Alert View
  - Incident View
- Search App
- Observed Attack Techniques
- Targeted Attack Detection
- Forensics and Analysis
  - War Room Tab
    - Workspaces
      - Adding Elements to an Investigation Timeline
  - Packages Tab
    - Evidence Collection
      - Manual Evidence Collection
      - Supported Evidence Types
- Managed Services
Threat Intelligence
- Campaign Intelligence
  - Threat Information Screen
- Intelligence Reports
- Suspicious Object Management
  - Suspicious Object List
  - Exception List
    - Adding Exceptions
- Sandbox Analysis
- Third-Party Intelligence
  - TAXII Feeds
    - Configuring a TAXII Feed
  - MISP Feeds
Workflow and Automation
- Security Playbooks
- Response Management
  - Response Actions
  - Response Data
- Third-Party Integration
- API Automation Center
- Service Gateway Management
Zero Trust Secure Access
- Getting Started with Zero Trust Secure Access
- Secure Access Overview
- Secure Access Rules
- Secure Access Resources
- Secure Access History
- Secure Access Configuration
- Troubleshooting Zero Trust Secure Access
Assessment
- Security Assessment Service
Endpoint Security Operations
- Endpoint Inventory 2.0
- Endpoint Inventory
  - Getting Started with XDR for Endpoints
  - Managing the Endpoint List in Endpoint Inventory 1.0
    - Endpoint List Settings in Endpoint Inventory 1.0
- Endpoint Policies
- Trend Cloud One - Endpoint & Workload Security
Network Security Operations
- Network Inventory
- Network Intrusion Prevention
Email Security Operations
- Email Account Inventory
  - Email Sensor Management
Mobile Security Operations
- Getting Started with Mobile Security
- Mobile Inventory
- Mobile Detection Logs
- Mobile Policy
  - Mobile Policy Data
  - Configuring Mobile Policies
- Risky Mobile Apps
  - Risky Mobile App Data
  - Approved List Data
Point Product Connections
- Product Connector
  - Connecting a Product
  - Required Settings on Supported Products
Account
- Single Sign-On
  - Configuring SAML Single Sign-On
- User Accounts
- User Roles
  - Configuring Custom User Roles
  - Predefined Roles
- Notifications
- Audit Logs
  - User Logs
    - User Log Data
  - System Logs
    - System Log Data
- Console Settings
- License Information
- Credit Usage
- Support Settings
Getting Help and Troubleshooting
- Help Kit
  - Toolbox Resources
  - Simulations
- Self-Diagnosis

Android Device Resource Consumption

View the results of Mobile Security performance tests on a Google Pixel 6.

Table 1. Tested Phone Specifications
Model	RAM	OS	Kernel Version	SDK Version
Google Pixel 6	8 GB	Android 13	5.10	1.05.6020

CPU Usage

The following chart shows the CPU resources used by Mobile Security as a percentage of total CPU usage.

Observations:

CPU usage increased during scanning and decreased rapidly after scan completion
CPU usage increased when detecting a suspicious URL in the browser

Conclusion:

The Mobile Security app did not exceed 35% of CPU resources on the tested device, and the average value was about 20% when CPU resources were used. The Mobile Security app used almost no CPU resources when idle.

Memory Usage

Observations:

Memory usage fluctuated significantly during scanning
Memory usage fluctuated slightly after detecting suspicious web URLs

Conclusion:

The Mobile Security app occupied not more than 400 MB while in use on the tested device, and the average value was about 300 MB when idle.

Network Usage

Observations:

Short-term peaks appeared when updating patterns

Conclusion:

On the tested device, Mobile Security occupied less than 1MB of network traffic most of the time.