Detailed breakdown of gathered data =================================== GNU/Linux Operating System -------------------------- barman crontab/cron (``barman_crontab_cron`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Output from crontab -l, if running as barman. Content of /etc/cron.d/barman, if exists. Report output: - file ``/linux/barman_cron.data`` : Content of /etc/cron.d/barman, if exists - file ``/linux/barman_crontab.data`` : Output from barman crontab -l, if barman user **Depth:** surface **Security Impact:** *low* — May have entries in crontab/cron with sensitive data debug_sources (``debug_sources`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Count files under ``/usr/src/debug`` to detect which applications’ source code is present in the system and facilitate live debugging. Report output: - file ``/linux/debug_sources.data`` : Sources for GNU debugger **Depth:** surface **Security Impact:** *low* — no known security impact. EFM CLI (``efm_cli`` ) ^^^^^^^^^^^^^^^^^^^^^^ Get output of efm cluster-status command. Report output: - file ``/tools/efm/cli/cluster_status.out`` : Output of ``efm cluster-status cluster_name`` command **Depth:** surface **Security Impact:** *low* — no known security impact. EFM configuration (``efm_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ EFM properties and nodes configuration files Report output: - file ``/tools/efm/config/efm.nodes`` : EFM nodes file - file ``/tools/efm/config/efm.properties`` : EFM properties file **Depth:** surface **Security Impact:** *low* — no known security impact. EFM systemctl (``efm_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When EFM services are detected, collects status and cat of the corresponding services. Will check for any service which name starts with ``edb-efm-`` Report output: - file ``/tools/efm/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/efm/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. etcd CLI (``etcd_cli`` ) ^^^^^^^^^^^^^^^^^^^^^^^^ Gathers the output of some ``etcdctl`` commands, if ``etcdctl`` is available in the server. The commands are: endpoint status and endpoint health. Report output: - file ``/tools/etcd/cli/endpoint_status.out`` : Output of ``etcdctl endpoint status`` command - file ``/tools/etcd/cli/endpoint_health.out`` : Output of ``etcdctl endpoint health`` command **Depth:** surface **Security Impact:** *low* — no known security impact. etcd configuration (``etcd_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collects etcd configuration file that is found in the server Report output: - file ``/tools/etcd/config/basename`` : etcd configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. etcd systemctl (``etcd_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When etcd services are detected, collects status and cat of the corresponding services. Will check for any service which name starts with ``etcd`` Report output: - file ``/tools/etcd/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/etcd/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. HARP CLI (``harp_cli`` ) ^^^^^^^^^^^^^^^^^^^^^^^^ Gathers output of a few ``harpctl`` command outputs using the ``config.yml`` file which is found in the server. The commands are: cluster, proxies, locations, nodes, and version. Report output: - file ``/tools/harp/cli/version.out`` : Output of ``harp -f conf_file_path version`` command - file ``/tools/harp/cli/proxies.out`` : Output of ``harp -f conf_file_path get proxies -o yaml`` command - file ``/tools/harp/cli/nodes.out`` : Output of ``harp -f conf_file_path get nodes -o yaml`` command - file ``/tools/harp/cli/locations.out`` : Output of ``harp -f conf_file_path get locations -o yaml`` command - file ``/tools/harp/cli/cluster.out`` : Output of ``harp -f conf_file_path get cluster -o yaml`` command **Depth:** surface **Security Impact:** *low* — no known security impact. HARP configuration (``harp_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collects HARP configuration file that is found in the server Report output: - file ``/tools/harp/config/harp.cluster.init.yml`` : HARP bootstrap configuration file - file ``/tools/harp/config/basename`` : HARP configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. HARP systemctl (``harp_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When HARP services are detected, collects status and cat of the corresponding services. Will check for any service which name starts with ``harp`` Report output: - file ``/tools/harp/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/harp/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. Block devices layout (``linux_block_devices_layout`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information on block devices layout from the ``lsblk`` command Report output: - file ``/linux/lsbk.data`` : ``lsbk`` command output **Depth:** surface **Security Impact:** *low* — no known security impact. Processor governor (``linux_cpu_governor`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Processor scaling governor from the files in ``/sys/devices/system/cpu`` Report output: - file ``/linux/sys/energy_perf_bias.data`` : Intel Performance and Energy Bias attributes - file ``/linux/sys/intel_pstate.data`` : Intel pstate configuration - file ``/linux/sys/cpu_scaling_driver.data`` : available CPU scaling driver - file ``/linux/sys/cpu_scaling_available_governors.data`` : available CPU scaling governors - file ``/linux/sys/cpu_scaling_governor.data`` : active CPU scaling governor **Depth:** surface **Security Impact:** *low* — no known security impact. Mounted file systems and available space (``linux_devices_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List mounted filesystems through the ``mount`` command and free space using ``df`` . Report output: - file ``/linux/diskspace.data`` : amount of available disk space - file ``/linux/mount.data`` : Output of the ``mount`` command **Depth:** surface **Security Impact:** *low* — no known security impact. File systems configuration (``linux_disk_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Disk configuration obtained through the ``/etc/fstab`` file Report output: - file ``/linux/fstab.data`` : contents of /etc/fstab **Depth:** surface **Security Impact:** *low* — no known security impact. OS distribution, kernel and device data (``linux_distro_collector`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information about the Linux distribution currently in use, as returned by the ``lsb_release`` command. Report output: - file ``/linux/release.data`` : The Linux distribution currently in use - file ``/linux/release_source.data`` : The name of the collected file or the executed command **Depth:** surface **Security Impact:** *low* — no known security impact. Hardware (``linux_hardware_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Hardware info through ``lspci`` Report output: - file ``/linux/lspci.data`` : Hardware info from ``lspci`` **Depth:** surface **Security Impact:** *low* — no known security impact. Hypervisor (``linux_hypervisor_collector`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information about the type of virtualization used, as returned by the ``systemd-detect-virt`` command. Report output: - file ``/linux/hypervisor.data`` : The name of the collected file or the executed command **Depth:** surface **Security Impact:** *low* — no known security impact. Kernel (``linux_kernel_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Kernel info, transparent huge pages status and disk scheduler configuration obtained by combining the output of the commands ``uname`` and ``ipcs`` with the contents of the ``/proc`` and ``/sys`` filesystems Report output: - file ``/linux/read_ahead.data`` : Info on the read ahead - file ``/linux/schedulers.data`` : Scheduler info from ``/sys`` dir - file ``/linux/sys/kernel_mm_transparent_hugepage.data`` : Transparent huge pages info - file ``/linux/ipcs.data`` : ``ipcs`` command output - file ``/linux/uname.data`` : ``uname`` command output **Depth:** surface **Security Impact:** *low* — no known security impact. Kernel limits (``linux_kernel_limits`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Configuration file for the ``pam_limits`` module Report output: - file ``/linux/limits.data`` : content of the ``limits.conf`` file **Depth:** surface **Security Impact:** *low* — no known security impact. Processor usage statistics (``linux_mpstat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Processor statistics from the ``mpstat`` command. Report output: - file ``/linux/mpstat.data`` : Output from ‘mpstat -P ALL 1 10’ **Depth:** surface **Security Impact:** *low* — no known security impact. Network interfaces (``linux_network_interfaces`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Network interface information from the ``ip`` and ``ifconfig`` commands. Report output: - file ``/linux/ifconfig.data`` : Output from ‘ifconfig’ - file ``/linux/ip_address_list.data`` : Output from ‘ip address list’ **Depth:** surface **Security Impact:** *low* — no known security impact. Installed packages via rpm or dpkg (``linux_packages_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information about the system packages installed using ``rpm`` or ``dpkg`` Report output: - file ``/linux/packages-dpkg.data`` : List of packages installed using ``dpkg`` - file ``/linux/packages-rpm.data`` : List of packages installed using ``rpm`` **Depth:** surface **Security Impact:** *low* — no known security impact. PostgreSQL disk layout (``linux_postgresql_disk_layout`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List all files in the PostgreSQL data directory using ``find`` for links and ``ls`` for files Report output: - file ``/linux/pg_ls.data`` : List of files inside the data directory - file ``/linux/pg_links.data`` : List of links inside the data directory **Depth:** surface **Security Impact:** *low* — no known security impact. SELinux (``linux_sestatus`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SELinux status from ``sestatus`` Report output: - file ``/linux/sestatus.data`` : Output from ‘setstatus’ **Depth:** surface **Security Impact:** *low* — no known security impact. System identification (``linux_system_identity`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect hostname, network interfaces, system info (uname), system identifier and release info. Report output: - file ``/linux/id/system_release.data`` : OS information from /etc/system-release - file ``/linux/id/os_release.data`` : OS information from /etc/os-release - file ``/linux/id/machine_id.data`` : Machine ID contained in /etc/machine-id - file ``/linux/id/uname.data`` : Information about the running kernel - file ``/linux/id/hostname.data`` : Fully qualified domain name - file ``/linux/id/interfaces.data`` : Network addresses of the host **Depth:** surface **Security Impact:** *low* — no known security impact. dmesg and /proc information (``linux_system_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System info from the contents of the ``/proc`` filesystem and through the output of ``dmesg`` command. Report output: - file ``/linux/lsmod.data`` : Lsmod output - file ``/linux/dmesg_with_timestamp.data`` : Dmesg output (human readable timestamps) - file ``/linux/dmesg.data`` : Dmesg output - file ``/linux/proc/sys_net_ipv4.data`` : Network info from ``/proc`` - file ``/linux/proc/sys_vm.data`` : vm info from ``/proc`` - file ``/linux/proc/sys_kernel.data`` : Kernel info from ``/proc`` - file ``/linux/vmstat.data`` : VM statistics from ``/proc`` - file ``/linux/proc/mounts.data`` : Mount points from ``/proc`` - file ``/linux/proc/uptime.data`` : Uptime info from ``/proc`` - file ``/linux/proc/loadavg.data`` : Load avg from ``/proc`` - file ``/linux/proc/meminfo.data`` : Memory info from ``/proc`` **Depth:** surface **Security Impact:** *low* — no known security impact. System status — iostat (``linux_system_status_iostat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``iostat`` command. Report output: - file ``/linux/iostat.data`` : Info on I/O statistics **Depth:** surface **Security Impact:** *low* — no known security impact. System status — nfsiostat (``linux_system_status_nfsiostat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``nfsiostat`` command. Report output: - file ``/linux/nfsiostat.data`` : nfs I/O statistics **Depth:** surface **Security Impact:** *low* — no known security impact. System status — ps (``linux_system_status_ps`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``ps`` command. Report output: - file ``/linux/ps.data`` : Active processes info **Depth:** surface **Security Impact:** *low* — Some processes might contain sensitive data in their names System status — sar (``linux_system_status_sar`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``sar`` command. Report output: - file ``/linux/sar.data`` : Actual ``sar`` info - file ``/linux/sar-yesterday.data`` : ``sar`` info from yesterday **Depth:** surface **Security Impact:** *low* — no known security impact. System status — top (``linux_system_status_top`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``top`` command. Report output: - file ``/linux/top.data`` : Process information **Depth:** surface **Security Impact:** *low* — Some processes might contain sensitive data in their names System status — vmstat (``linux_system_status_vmstat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ System status from the ``vmstat`` command. Report output: - file ``/linux/vmstat.data`` : Info on processes, memory, paging, block IO, traps, disks and cpu activity **Depth:** surface **Security Impact:** *low* — no known security impact. systemctl units (``linux_systemctl_units`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Systemctl list-units on a ``systemd`` server Report output: - file ``/linux/systemctl-list-units.data`` : Output of ‘systemctl list-units’ **Depth:** surface **Security Impact:** *low* — no known security impact. tuned (``linux_tuned`` ) ^^^^^^^^^^^^^^^^^^^^^^^^ Tuned status and profiles Report output: - directory ``/linux/tuned/tune-profiles`` : Files from ``/etc/tune-profiles`` - directory ``/linux/tuned/tuned`` : Files from ``/etc/tuned`` - file ``/linux/tuned/tuned.conf`` : The file ``/etc/tuned.conf`` - file ``/linux/tuned/tuned-list.data`` : Output from ``tuned_adm list`` - file ``/linux/tuned/tuned-active.data`` : Output from ``tuned_adm active`` **Depth:** surface **Security Impact:** *low* — no known security impact. PEM configuration (``pem_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PEM configuration files from PEM agent, PEM server, and PEM Web server Report output: - file ``/tools/pem/config/edb-ssl-pem.conf`` : PEM Web server SSL configuration file - file ``/tools/pem/config/edb-pem.conf`` : PEM Web server configuration file - file ``/tools/pem/config/install-config`` : PEM server configuration file (installation config file) - file ``/tools/pem/config/config_setup.py`` : PEM server setup configuration file - file ``/tools/pem/config/pem.wsgi`` : PEM server WSGI definition file - file ``/tools/pem/config/agent.cfg`` : PEM agent configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. PEM systemctl (``pem_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When PEM is detected, collects PEM agent and PEM web server status and content Report output: - file ``/tools/pem/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/pem/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. PgBouncer configuration (``pgbouncer_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PgBouncer configuration files Report output: - file ``/tools/pgbouncer/num/config/basename`` : PgBouncer configuration file from instance num **Depth:** surface **Security Impact:** *low* — no known security impact. PgBouncer systemctl (``pgbouncer_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When PgBouncer services are detected, collects status and cat of the corresponding services. Will check for any service which contains any of the PgBouncer configuration files Report output: - file ``/tools/pgbouncer/num/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name from instance num - file ``/tools/pgbouncer/num/systemd/service_name_status.data`` : Output of ’systemctl status service_name from instance num **Depth:** surface **Security Impact:** *low* — no known security impact. PGD Proxy configuration (``pgd_proxy_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collects PGD Proxy configuration file that is found in the server Report output: - file ``/tools/pgd-proxy/config/basename`` : PGD Proxy configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. PGD Proxy systemctl (``pgd_proxy_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When PGD Proxy services are detected, collects status and cat of the corresponding services. Will check for any service which name starts with ``pgd-proxy`` Report output: - file ``/tools/pgd-proxy/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/pgd-proxy/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. postgres/enterprisedb crontab (``postgres_enterprisedb_crontab`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Output from crontab -l, if running as postgres or enterprisedb Report output: - file ``/linux/enterprisedb_crontab.data`` : Output from enterprisedb crontab -l, if enterprisedb user - file ``/linux/postgres_crontab.data`` : Output from postgres crontab -l, if postgres user **Depth:** surface **Security Impact:** *low* — May have entries in crontab/cron with sensitive data repmgr CLI (``repmgr_cli`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collects output of ``repmgr cluster crosscheck`` and ``repmgr daemon status`` using the repmgr.conf file which is found in the server. Report output: - file ``/tools/repmgr/cli/daemon_status.out`` : Output of ``repmgr daemon status -f conf_file_path`` command - file ``/tools/repmgr/cli/cluster_crosscheck.out`` : Output of ``repmgr cluster crosscheck -f conf_file_path`` command **Depth:** surface **Security Impact:** *low* — no known security impact. repmgr configuration (``repmgr_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collects repmgr configuration file that is found in the server Report output: - file ``/tools/repmgr/config/repmgr.conf`` : repmgr configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. repmgr systemctl (``repmgr_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When repmgr services are detected, collects status and cat of the corresponding services. Will check for any service which name starts with ``repmgr`` Report output: - file ``/tools/repmgr/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/repmgr/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. xDB CLI (``xdb_cli`` ) ^^^^^^^^^^^^^^^^^^^^^^ xDB output from several CLI commands, from the xDB publication and/or subscription server that are running. Report output: - directory ``/tools/xdb/cli`` : xDB CLI print commands **Depth:** surface **Security Impact:** *low* — no known security impact. xDB configuration (``xdb_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xDB configuration files Report output: - file ``/tools/xdb/config/xdbReplicationServer.config`` : xDB startup configuration\` - file ``/tools/xdb/config/edb-repl.conf`` : xDB replication configuration\` - file ``/tools/xdb/config/xdb_subserver.conf`` : xDB subscription server configuration - file ``/tools/xdb/config/xdb_pubserver.conf`` : xDB publication server configuration **Depth:** surface **Security Impact:** *low* — no known security impact. xDB systemctl (``xdb_systemctl`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When xDB services are detected, collects status and cat of edb- xdbpubserver and edb-xdbsubserver Report output: - file ``/tools/xdb/systemd/service_name_cat.data`` : Output of ’systemctl cat service_name - file ``/tools/xdb/systemd/service_name_status.data`` : Output of ’systemctl status service_name **Depth:** surface **Security Impact:** *low* — no known security impact. Microsoft Windows Operating System ---------------------------------- PEM configuration — Windows (``pem_configuration_windows`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PEM configuration files from PEM agent, PEM server, and PEM Web server in a Windows environment. Report output: - file ``/tools/pem/config/edb-ssl-pem.conf`` : PEM Web server SSL configuration file - file ``/tools/pem/config/edb-pem.conf`` : PEM Web server configuration file - file ``/tools/pem/config/pem.wsgi`` : PEM server WSGI definition file - file ``/tools/pem/config/agent.cfg`` : PEM agent configuration file **Depth:** surface **Security Impact:** *low* — no known security impact. PEM sc (``pem_sc`` ) ^^^^^^^^^^^^^^^^^^^^ When PEM is detected, collects PEM agent and PEM web server status and content Report output: - file ``/tools/pem/sc/service_name_query.data`` : Output of ’sc query service_name **Depth:** surface **Security Impact:** *low* — no known security impact. Disk information (``win_disk_information`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Disk and controller information from the system registry. Report output: - file ``/windows/enum_ide.reg`` : Local machine ide device settings - file ``/windows/enum_scsi.reg`` : Local machine scsi device settings **Depth:** surface **Security Impact:** *low* — no known security impact. Hosts file (``win_hosts`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Host files and network related information Report output: - file ``/windows/services.data`` : Windows ``services`` file - file ``/windows/protocol.data`` : Windows ``protocol`` file - file ``/windows/networks.data`` : Windows ``networks`` file - file ``/windows/hosts.sam`` : Windows ``hosts.sam`` file - file ``/windows/hosts.data`` : Windows ``hosts`` file **Depth:** surface **Security Impact:** *low* — no known security impact. MsInfo (``win_msinfo`` ) ^^^^^^^^^^^^^^^^^^^^^^^^ ``MsInfo32`` report in ``NFO`` and ``TXT`` format Report output: - file ``/windows/msinfo_report.txt`` : Information from the ``MsInfo32`` in textual format - file ``/windows/msinfo_report.nfo`` : Information from the ``MsInfo32`` in ``NFO`` **Depth:** surface **Security Impact:** *low* — no known security impact. ODBC/64 (``win_odbc32_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ODBC configuration from the 64 bit registry section Report output: - file ``/windows/user_odbc_wow64.reg`` : User DSN list - file ``/windows/localmachine_odbcinst_wow64.reg`` : List of installed ODBC drivers - file ``/windows/localmachine_odbc_wow64.reg`` : System DSN list **Depth:** surface **Security Impact:** *medium* — ODBC connection information could expose the presence of other databases or connection information to PostgreSQL that can be used to attack the system ODBC/32 (``win_odbc64_info`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ODBC configuration from the 32 bit registry section Report output: - file ``/windows/user_odbc.reg`` : User DSN list - file ``/windows/localmachine_odbcinst.reg`` : list of installed ODBC drivers - file ``/windows/localmachine_odbc.reg`` : System DSN list **Depth:** surface **Security Impact:** *medium* — ODBC connection information could expose the presence of other databases or connection information to PostgreSQL that can be used to attack the system systeminfo (``win_systeminfo`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Output of the ``systeminfo`` command Report output: - file ``/windows/systeminfo_report.txt`` : Information from the ``systeminfo`` command **Depth:** surface **Security Impact:** *low* — no known security impact. Disk volumes (``win_volumes`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Volume list from ``WMI`` Report output: - file ``/windows/association_structure`` : Association between drive letters and physical drives - file ``/windows/volume_disk`` : Volume list from the WMI subsystem - file ``/windows/logical_disk_list`` : Logical disk list from the WMI subsystem - file ``/windows/disk_partition_list`` : Disk partition list from the WMI subsystem - file ``/windows/disk_drive_list`` : Disk list from the WMI subsystem **Depth:** surface **Security Impact:** *low* — no known security impact. xDB CLI — Windows (``xdb_cli_windows`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xDB output from several CLI commands, from the xDB publication and/or subscription server that are running. Report output: - directory ``/tools/xdb/cli`` : xDB CLI print commands **Depth:** surface **Security Impact:** *low* — no known security impact. xDB configuration — Windows (``xdb_configuration_windows`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ xDB configuration files Report output: - file ``/tools/xdb/config/xdbReplicationServer.config`` : xDB startup configuration\` - file ``/tools/xdb/config/edb-repl.conf`` : xDB replication configuration\` - file ``/tools/xdb/config/xdb_subserver.conf`` : xDB subscription server configuration - file ``/tools/xdb/config/xdb_pubserver.conf`` : xDB publication server configuration **Depth:** surface **Security Impact:** *low* — no known security impact. xDB sc (``xdb_sc`` ) ^^^^^^^^^^^^^^^^^^^^ When xDB is detected, collects xDB Publication and Subscription server status Report output: - file ``/tools/xdb/sc/service_name_query.data`` : Output of ’sc query service_name **Depth:** surface **Security Impact:** *low* — no known security impact. PostgreSQL/BDR3 Instance ------------------------ Current archiver stats (``postgresql_archiver`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Statistics about the archiver process’s activity (from pg_stat_archiver) Report output: - file ``postgresql/archiver.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Available extensions (``postgresql_available_extensions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of extensions available on the server Report output: - file ``postgresql/available_extensions.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current bg_writer stats (``postgresql_bgwriter`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Statistics about the background writer process’s activity (from pg_stat_bgwriter) Report output: - file ``postgresql/bgwriter.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Directory with binaries (``postgresql_bin_dir`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL binary directory Report output: - file ``/postgresql/postgresql_bin_path.data`` : Path to the PostgreSQL bin directory **Depth:** surface **Security Impact:** *low* — no known security impact. Current configuration (``postgresql_configuration`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL current configuration Report output: - file ``postgresql/configuration.out`` **Depth:** surface **Security Impact:** *medium* — postgresql.conf might contain bad security policies Configuration files (``postgresql_configuration_files`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL configuration files and the data directory path (passwords contained in well-known connection strings are automatically redacted for information security reasons). Report output: - file ``/postgresql/pg_ident.conf`` : PostgreSQL ident configuration file - file ``/postgresql/pg_hba.conf`` : PostgreSQL host-based authentication file - file ``/postgresql/postgresql.auto.conf`` : PostgreSQL auto configuration file - file ``/postgresql/recovery.done`` : PostgreSQL recovery.done file - file ``/postgresql/recovery.conf`` : PostgreSQL recovery.conf file - file ``/postgresql/postgresql.conf`` : PostgreSQL configuration file **Depth:** surface **Security Impact:** *medium* — ``pg_hba.conf`` and ``pg_ident.conf`` might expose potential security holes such as trusted connections. Databases (``postgresql_databases`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of databases in the PostgreSQL node Report output: - file ``postgresql/databases.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. postgresql_db_bdr_tables_and_views (``postgresql_db_bdr_tables_and_views`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect all the tables and views of the BDR extension, except for: - bdr.apply_log — bdr.conflict_history — bdr.consensus_kv_data - bdr.internal_node_pre_commit — bdr.replication_status - bdr.state_journal — bdr.stat_activity Report output: - file ``/postgresql/dbs/dbname/bdr/*`` : Content of all tables under the BDR schema **Depth:** shallow **Security Impact:** *low* — no known security impact. postgresql_db_pglogical_tables_and_views (``postgresql_db_pglogical_tables_and_views`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect all the tables and views of the pglogical extension Report output: - file ``/postgresql/dbs/dbname/pglogical/*`` : Content of all tables under the pglogical schema **Depth:** shallow **Security Impact:** *low* — no known security impact. Database/Role Setting (``postgresql_db_role_setting`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of database/role settings in the PostgreSQL node Report output: - file ``postgresql/db_role_setting.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Node and snapshot data (``postgresql_node`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information about the running PostgreSQL node Report output: - file ``postgresql/node.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. pg_config (``postgresql_pg_config`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL ``pg_config`` command output. Report output: - file ``/postgresql/pg_config.data`` : ``pg_config`` command output **Depth:** surface **Security Impact:** *low* — no known security impact. pg_controldata (``postgresql_pg_controldata`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL ``pg_controldata`` information. Report output: - file ``/postgresql/pg_controldata.data`` : ``pg_controldata`` command output **Depth:** surface **Security Impact:** *low* — no known security impact. Version (``postgresql_pg_version`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL client and server version. Report output: - file ``/postgresql/postgresql_server_version.data`` : PostgreSQL server version - file ``/postgresql/postgresql_client_version.data`` : PostgreSQL client version **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_prepared_xacts contents (``postgresql_prepared_xacts`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Status of prepared xacts (from pg_prepared_xacts) Report output: - file ``postgresql/prepared_xacts.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_replication_origin_status contents (``postgresql_replication_origin`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Status of replication origins (from pg_replication_origin_status) Report output: - file ``postgresql/replication_origins.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_replication_slots contents (``postgresql_replication_slots`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Replication slots (from pg_replication_slots) Report output: - file ``postgresql/replication_slots.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Roles (``postgresql_roles`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Database roles from ``pg_roles`` Report output: - file ``postgresql/roles.out`` **Depth:** shallow **Security Impact:** *medium* — pg_roles might contain bad security policies Current activity stats (``postgresql_running_activity`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information related to the current activity on running processes (from ``pg_stat_activity`` ) Report output: - file ``postgresql/running_activity.out`` **Depth:** shallow **Security Impact:** *low* — queries in ``pg_stat_activity`` could contain user names and application names. Active locks (``postgresql_running_locks`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of active locks Report output: - file ``postgresql/running_locks.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. pg_server_limits (``postgresql_server_limits`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Real effective kernel OS limits for the postmaster PID. Report output: - file ``/postgresql/pg_server_limits_PORT.data`` : ``prlimit`` for postmaster PID **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_shmem_allocations contents (``postgresql_shmem_allocations`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Status of shared memory allocations (from pg_shmem_allocations) Report output: - file ``postgresql/shmem_allocations.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_stat_progress_analyze contents (``postgresql_stat_progress_analyze`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ANALYZE progress Report output: - file ``postgresql/pg_stat_progress_analyze.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_stat_progress_basebackup contents (``postgresql_stat_progress_basebackup`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ BASEBACKUP progress Report output: - file ``postgresql/pg_stat_progress_basebackup.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_stat_progress_copy contents (``postgresql_stat_progress_copy`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ COPY progress Report output: - file ``postgresql/pg_stat_progress_copy.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_stat_progress_vacuum contents (``postgresql_stat_progress_vacuum`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ VACUUM progress Report output: - file ``postgresql/pg_stat_progress_vacuum.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Current pg_stat_replication contents (``postgresql_stat_replication`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Replication connections (from pg_stat_replication) Report output: - file ``postgresql/replication.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Server subscription statistics (``postgresql_subscription_statistics`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Statistics of subscriptions Report output: - file ``postgresql/subscription_statistics.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Server subscriptions (``postgresql_subscriptions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of subscriptions Report output: - file ``postgresql/subscriptions.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Tablespaces (``postgresql_tablespaces`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Tablespaces information and location Report output: - file ``postgresql/tablespaces.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Workload characteristics using waits (``postgresql_waits_stats`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ PostgreSQL workload characterisation using built-in wait events Report output: - file ``postgresql/running_waits_sample.out`` : Workload characterisation using built-in wait events **Depth:** surface **Security Impact:** *low* — no known security impact. Details for every PostgreSQL/BDR3 Database ------------------------------------------ BDR1 replication slots (``postgresql_db_bdr1_replication_slots`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of replication slots with 9.6 format for BDR1 Report output: - file ``bdr1_replication_slots.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR2 replication slots (``postgresql_db_bdr2_replication_slots`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of replication slots with 9.6 format for BDR2 Report output: - file ``bdr2_replication_slots.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR conflict_history_summary aggregation (``postgresql_db_bdr3_conflict_history_summary_agg`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect aggregate count for all types of conflicts Report output: - file ``bdr_conflict_history_summary_agg.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR current activity stats (``postgresql_db_bdr3_stat_activity`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information related to the current activity on running processes (from ``bdr.stat_activity`` ) Report output: - file ``bdr_stat_activity.out`` **Depth:** shallow **Security Impact:** *low* — queries in ``bdr.stat_activity`` could contain user names and application names. BDR sequences (``postgresql_db_bdr_sequences`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of the BDR sequences Report output: - file ``bdr_sequences.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR version (``postgresql_db_bdr_version`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Currently used version of BDR Report output: - file ``bdr_version.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Database extensions (``postgresql_db_extensions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of extensions in the database Report output: - file ``extensions.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database indexes (``postgresql_db_indexes`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of indexes in the database Report output: - file ``indexes.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database procedural languages (``postgresql_db_languages`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Procedural languages in the database Report output: - file ``language.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. BDR monitor_group_raft (``postgresql_db_monitor_group_raft`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Check the raft status in the bdr cluster Report output: - file ``bdr_monitor_group_raft.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR monitor_group_versions (``postgresql_db_monitor_group_versions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Check the version of all BDR nodes Report output: - file ``bdr_monitor_group_versions.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. BDR monitor_local_replslots (``postgresql_db_monitor_local_replslots`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Check all the replication slot status Report output: - file ``bdr_monitor_local_replslots.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Database operators (``postgresql_db_operators`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Operators in the database Report output: - file ``operator.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database partitioned tables (``postgresql_db_partitioned_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Information about partitioned tables (using declarative partitioning) Report output: - file ``partitioned_table.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.agent table tuples (``postgresql_db_pem_agent`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.agent Report output: - file ``pem_agent.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.agent_config table tuples (``postgresql_db_pem_agent_config`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.agent_config Report output: - file ``pem_agent_config.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.agent_heartbeat table tuples (``postgresql_db_pem_agent_heartbeat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.agent_heartbeat Report output: - file ``pem_agent_heartbeat.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.agent_server_binding table tuples (``postgresql_db_pem_agent_server_binding`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.agent_server_binding Report output: - file ``pem_agent_server_binding.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.config table tuples (``postgresql_db_pem_config`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.config Report output: - file ``pem_config.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.email_group table tuples (``postgresql_db_pem_email_group`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.email_group Report output: - file ``pem_email_group.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.email_group_option table tuples (``postgresql_db_pem_email_group_option`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.email_group_option Report output: - file ``pem_email_group_option.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.probe table tuples (``postgresql_db_pem_probe`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.probe Report output: - file ``pem_probe.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.probe_schedule table tuples (``postgresql_db_pem_probe_schedule`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.probe_schedule Report output: - file ``pem_probe_schedule.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.schema_version() output (``postgresql_db_pem_schema_version`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Output from function pem.schema_version() Report output: - file ``pem_schema_version.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.server table tuples (``postgresql_db_pem_server`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.server Report output: - file ``pem_server.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.server_heartbeat table tuples (``postgresql_db_pem_server_heartbeat`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.server_heartbeat Report output: - file ``pem_server_heartbeat.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.smtp_spool table tuples (``postgresql_db_pem_smtp_spool`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.smtp_spool Report output: - file ``pem_smtp_spool.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database PEM pem.snmp_spool table tuples (``postgresql_db_pem_snmp_spool`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable pem.snmp_spool Report output: - file ``pem_snmp_spool.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Pglogical subscription status (``postgresql_db_pglogical_subscription_status`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of tables replicated by pglogical Report output: - file ``pglogical_subscription_status.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Database functions (``postgresql_db_procs`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Functions in the database Report output: - file ``proc.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database publication tables (``postgresql_db_publication_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of tables of publications of the database Report output: - file ``publication_tables.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database publications (``postgresql_db_publications`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of publications of the database Report output: - file ``publications.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database repmgr repmgr.events table tuples (``postgresql_db_repmgr_events`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable repmgr.events Report output: - file ``repmgr/events.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database repmgr repmgr.monitoring_history table tuples (``postgresql_db_repmgr_monitoring_history`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable repmgr.monitoring_history Report output: - file ``repmgr/monitoring_history.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database repmgr repmgr.nodes table tuples (``postgresql_db_repmgr_nodes`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable repmgr.nodes Report output: - file ``repmgr/nodes.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database repmgr repmgr.replication_status table tuples (``postgresql_db_repmgr_replication_status`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable repmgr.replication_status Report output: - file ``repmgr/replication_status.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database repmgr repmgr.show_nodes table tuples (``postgresql_db_repmgr_show_nodes`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable repmgr.show_nodes Report output: - file ``repmgr/show_nodes.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database schema (``postgresql_db_schemas`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of schemas in the database Report output: - file ``schemas.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database statistics (``postgresql_db_statistics`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Statistics of the database Report output: - file ``statistics.out`` **Depth:** deep **Security Impact:** *low* — no known security impact. Database subscription tables (``postgresql_db_subscription_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of tables of subscriptions of the database Report output: - file ``subscription_tables.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database tables (``postgresql_db_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ List of tables in the database Report output: - file ``tables.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database types (``postgresql_db_types`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Types in the database Report output: - file ``type.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.xdb_mmr_pub_group table tuples (``postgresql_db_xdb_mmr_pub_group`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable \_edb_replicator_pub.xdb_mmr_pub_group Report output: - file ``xdb_mmr_pub_group.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.xdb_pub_database table tuples (``postgresql_db_xdb_pub_database`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable \_edb_replicator_pub.xdb_pub_database Report output: - file ``xdb_pub_database.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.xdb_pub_replog table tuples (``postgresql_db_xdb_pub_replog`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Last 50 rows from metatable \_edb_replicator_pub.xdb_pub_replog Report output: - file ``xdb_pub_replog.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.xdb_publication_subscriptionstable tuples (``postgresql_db_xdb_publication_subscriptions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable_edb_replicator_pub.xdb_publication_subscriptions Report output: - file ``xdb_publication_subscriptions.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.xdb_publications table tuples (``postgresql_db_xdb_publications`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable \_edb_replicator_pub.xdb_publications Report output: - file ``xdb_publications.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.rrep_mmr_pub_group table tuples (``postgresql_db_xdb_rrep_mmr_pub_group`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable \_edb_replicator_pub.rrep_mmr_pub_group Report output: - file ``xdb_rrep_mmr_pub_group.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.rrep_mmr_txset table tuples (``postgresql_db_xdb_rrep_mmr_txset`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Last 10 rows from metatable \_edb_replicator_pub.rrep_mmr_txset Report output: - file ``xdb_rrep_mmr_txset.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.rrep_properties table tuples (``postgresql_db_xdb_rrep_properties`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from from metatable \_edb_replicator_pub.rrep_properties Report output: - file ``xdb_rrep_properties.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.rrep_publication_tablestable tuples (``postgresql_db_xdb_rrep_publication_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from from metatable_edb_replicator_pub.rrep_publication_tables Report output: - file ``xdb_rrep_publication_tables.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Database xDB \_edb_replicator_pub.rrep_txset table tuples (``postgresql_db_xdb_rrep_txset`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Data from metatable \_edb_replicator_pub.rrep_txset Report output: - file ``xdb_pub_rrep_txset.out`` **Depth:** shallow **Security Impact:** *low* — no known security impact. Oracle-compatibile partitioning key view (``postgresql_epas_all_part_key_columns`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Provides partitioning key details (all_part_key_columns, EPAS specific) Report output: - file ``epas_all_part_key_columns.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Oracle-compatibile all partitioned table view (``postgresql_epas_all_part_tables`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ All partitioned tables view (from all_part_tables, EPAS specific) Report output: - file ``epas_all_part_tables.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Oracle-compatibile subpartitioning key view (``postgresql_epas_all_subpart_key_columns`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Provides subpartitioning key details (all_subpart_key_columns, EPAS specific) Report output: - file ``epas_all_subpart_key_columns.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Oracle-compatibile all table partitions view (``postgresql_epas_all_tab_partitions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ All partitions of all partitioned tables view (all_tab_partitions, EPAS specific) Report output: - file ``epas_all_tab_partitions.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Oracle-compatibile all table subpartitioning view (``postgresql_epas_all_tab_subpartitions`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ All subpartitions of all partitioned tables view (all_tab_subpartitions, EPAS specific) Report output: - file ``epas_all_tab_subpartitions.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. EPAS specific dblink information (``postgresql_epas_dblink`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Current EPAS dblink information from edb_dblink) Report output: - file ``epas_dblink.out`` **Depth:** surface **Security Impact:** *low* — no known security impact. Barman (Backup and Recovery Manager) ------------------------------------ Barman check (``barman_check`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect the status of the Barman ``check`` framework for all configured servers. Report output: - file ``/barman/barman_check.data`` : Output of ``barman check`` **Depth:** surface **Security Impact:** *low* — no known security impact. Barman diagnose (``barman_diagnose`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect the barman diagnosis information Report output: - file ``/barman/diagnose.data`` : Output from ‘barman diagnose’ **Depth:** surface **Security Impact:** *low* — no known security impact. Barman executable location (``barman_executable`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect the ‘barman’ executable location Report output: - file ``/barman/barman_location.data`` : The path of the main barman executable **Depth:** surface **Security Impact:** *low* — no known security impact. Barman module location (``barman_modules_path`` ) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Collect the location of the ‘barman’ Python modules Report output: - file ``/barman/barman_python_verbose.data`` : The list of Barman python modules **Depth:** surface