Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
System Security Guide
The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
Security Policies
Although QNX OS allows a process to set which operations it is permitted to do, a better option is to use the system’s security policies functionality.
The libsecpolev API (libsecpolev.h)
The libsecpolev library API provides functions that allow a program to monitor system trace events that relate to the successful or failed use of privileges covered by security policies.
secpolev_get_process_name()
Get the name of the process associated with an event

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components & Operations
- Graphics
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
  - Security Features Overview
  - Security for Developers
  - Security for System Integrators
  - Abilities
  - Security Policies
    Although QNX OS allows a process to set which operations it is permitted to do, a better option is to use the system’s security policies functionality.
    - Implementing security policies
    - Using security policy types
    - Security policy language
    - Named range file
    - Monitoring security policy events
    - Developing systems with a security policy
      In most development environments, security policies need to be revised or updated as a project progresses. For example, your initial attempt at a policy may not account for all desired behavior, or you might add a new program or new version of a program.
    - The error file
      The secpolgenerate utility provides the file /dev/secpolgenerate/errors to help you debug broken systems.
    - System monitoring using secpolgenerate
      In addition to development tasks, you can use secpolgenerate in a secure, deployed system to detect errors.
    - Security policy maintenance
      Maintenance tasks for your security policy can include determining whether any generated rules should be edited or removed, manually editing policies for efficiency and simplicity, and reviewing the contents of /dev/secpolgenerate/unused.
    - Reviewing for unnecessary rules
      Although secpolgenerate generates policy rules based on what was needed when the system was run, it's likely not all the rules are appropriate. QNX recommends that you review the security policy specifically to locate processes with abilities that they don't need.
    - State and event files
      The secpolgenerate utility uses files called state and event files to represent the successful or failed use of abilities and paths by processes according to their type.
    - Troubleshooting and frequently asked questions
    - The libsecpol API (secpol.h)
      The libsecpol library API provides functions for systems that use security policies.
    - The libsecpolev API (libsecpolev.h)
      The libsecpolev library API provides functions that allow a program to monitor system trace events that relate to the successful or failed use of privileges covered by security policies.
      - Flags for secpolev_get_ability_info()
      - Flags for secpolev_wait_event()
      - secpolev_event_type_t
        Security policy event types
      - secpolev_flush()
        Flush events so that they are received immediately
      - secpolev_get_ability_info()
        Get information about an ability event
      - secpolev_get_custom_perm_info()
        Get information about a custom permission event
      - secpolev_get_dropped_count()
        Get the number of dropped events
      - secpolev_get_path_info()
        Get information about a path event
      - secpolev_get_pid()
        Get the process ID associated with an event
      - secpolev_get_process_name()
        Get the name of the process associated with an event
      - secpolev_get_process_type()
        Get the type of the process associated with an event
      - secpolev_get_timestamp()
        Return the timestamp associated with the last event received
      - secpolev_init()
        Initiate event monitoring
      - secpolev_log()
        Log a message using the log callback
      - secpolev_log_callback_t
        Structure for error logging
      - secpolev_path_event_status_t
        Path event statuses
      - secpolev_set_log_callback()
        Set a callback for error logging
      - secpolev_shutdown()
        Request termination of event monitoring
      - secpolev_shutdown_type_t
        Shutdown types
      - secpolev_vlog()
        Log a message using the log callback (varargs)
      - secpolev_wait_event()
        Wait for the next event
  - Fortified System Functions
  - Pathtrust
    The pathtrust feature prevents processes from executing untrusted code. If a process is compromised, pathtrust mitigates the threat of the system being further compromised by an attacker using chained-together exploits.
  - Using mkqnximage to Display Security Features
  - Abilities Reference
  - Security Matrix
    The following table describes security problems and cyberattacks and the QNX OS security features that can mitigate them.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor and QNX Hypervisor for Safety
The QNX Hypervisor and QNX Hypervisor for Safety products allow you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

secpolev_get_process_name()

Get the name of the process associated with an event

Synopsis:

#include <secpol/secpolev.h>

const char * secpolev_get_process_name(void)

Library:

libsecpolev

Description:

The secpolev_get_process_name() function returns the name of the process associated with the last event received, or NULL, if not known. There are typically a few ability checks that are tested before a process gets a name (e.g., prot_exec and map_fixed).

Note that in the initial stage of an exec*() call, the process has no name, but this is not considered an error and errno is not set.

The returned string remains valid until the next call to secpolev_wait_event().

Returns:

The process name. If there is no current event or the process name is unknown, NULL is returned. errno is set to ENOTSUP if there is no current event.

Page updated: June 11, 2026