User Guides
CTE-U Quick Start Guide
- Terminology and Components
- Install and Configure CTE-U with CipherTrust Manager
  - Installation Prerequisites
  - Installation and Registration
  - Verifying Package Signatures
  - Setting the SE Linux state
- Guarding with CTE-U and CipherTrust Manager
  - Access the CipherTrust Manager Domain
  - Create an Encryption Key
  - Guarding CTE files with CTE-U
- Exporting GuardPoints over NFS
- Migrating CTE Agents to CTE-U
- Multifactor Authentication for CTE-U
  - Introduction to Multifactor Authentication
  - Using [CTE-U,MFA]
  - Use Cases for MFA on CTE
  - Exempting some users from authentication with a Whitelist
  - Setting up Multifactor Authentication with a One-Time-Password
  - Setting up Multifactor Authentication with an Inactivity Time Out
  - Administrator Tasks for Multifactor Authentication
  - Troubleshooting Multifactor Authentication
CTE-U Health Manager Utility
- Performing Health Check
- Using the Monitor
- Service Commands
- Viewing the Service Status
- Gathering the Technical Dump
- Troubleshooting/ Debugging CTE-U
CTE-U Agent Advanced Configuration Guide for Linux
- CTE-U Overview
- Getting Started
  - Configuring CTE-U with CipherTrust Manager
- Enhanced Encryption Mode
- CTE with systemd
  - CTE Agent Control Changes on systemd
- Utilities
  - CTE-U Linux Authentication and Client Settings
  - Individual GuardPoint Tuning
  - Secfsd Utility
- Upgrading CTE-U on Linux
- Uninstalling CTE-U from Linux
Using FreeBSD with CTE-U
- FreeBSD Jail
- Install CTE-U Dependencies
- FreeBSD Services
- Upgrade CTE-U Packages
- Remove CTE-U Packages
- Unsupported Features for CTE-U with FreeBSD

Using the Monitor

Run the monitor command to view and/or modify the log level and other configurations interactively. To use the monitor:

sudo /usr/bin/cte_u_manager  monitor

The main monitor console appears, as shown below.

Console

Monitor Syslog Service

When the CTE-U Health Manager is running in the monitor mode, any issues are logged to the configured Syslog server. For example, if you attach a debugger to one of the secfs_fuse processes, then when it detaches it from the process, the following messages are logged to the Syslog server:

Dec 29 06:56:42 localhost cte_u_manager[28394]: Error: gdb (PID 28628) is attached to 100675.
Dec 29 06:56:52 localhost cte_u_manager[28394]: Recovered: gdb (PID 28628) is attached to 100675.

Suggest A Change

Using the Monitor

Monitor Syslog Service

On this page