Informix Security Review: Scripts and Usage
A read-only evidence collector for Informix® security reviews, and a small script that downloads it and checks its checksum before you run anything.
ifx_secaudit.sh runs the checks from the Oninit security review
checklist against one Informix instance and writes the result as a CSV, a short
summary and the raw evidence behind every finding. It never changes configuration.
It runs onstat, onaudit -c and -o, and
SELECT/UNLOAD statements, and nothing else.
The checks themselves are described in this set: method and severity, the eight check groups (A, B, C, D, E, F, G, H), the version matrix, the report template and example results.
1. What you need
- Informix 11.50, 11.70, 12.10, 14.10 or 15.0, on Linux, AIX, Solaris or HP-UX. Windows instances are not supported by the script.
bashorksh93, and the Informix client tools (onstat,onaudit,dbaccess). Nothing else needs installing.- The instance environment set:
INFORMIXDIR,INFORMIXSERVER,ONCONFIG,PATHincluding$INFORMIXDIR/bin, and optionallyINFORMIXSQLHOSTS. - The right user. Run it as user
informix, or as the DBSA of a non-root installation. A second run as root adds the checks theinformixuser cannot see (/etc/shadowlock state,/etc/informix/allowed.surrogates, other users’ trust files).
Whether a check applies is decided by whether the parameter or catalog table exists
on your instance, not by a version number, so a check that does not apply reports
NA instead of a false failure.
2. Usage
ifx_secaudit.sh [-o outdir] [-d "db1 db2 ..."] [-u owner] [-g group] [-h]
| Option | Meaning | Default |
|---|---|---|
-o outdir | Output directory | ./ifx_secaudit_<host>_<server>_<timestamp> |
-d dbs | Only these databases, space-separated and quoted | every database in sysmaster:sysdatabases |
-u owner | Expected owner of chunks and configuration files | informix |
-g group | Expected DBSA group | informix |
-h | Print usage |
3. Examples
Review a whole instance, as user informix with the environment set:
. ~informix/.profile # or however you set INFORMIXDIR, INFORMIXSERVER, ONCONFIG
./ifx_secaudit.sh
Only some databases:
./ifx_secaudit.sh -d "stores sales"
A non-root installation, where the owner and DBSA group are not
informix:
./ifx_secaudit.sh -u ifxadm -g ifxdba
Second pass as root, for the checks informix cannot see.
Keep the results beside the first run:
sudo -E ./ifx_secaudit.sh -o ./ifx_secaudit_root_pass
Fetch a later release: fetch_secaudit.sh ships in the package.
It downloads a release and its .sha256 file from a location that serves them directly
(for example your own mirror), refuses to unpack anything whose checksum does not match
(exit 4), and never runs the collector.
sh fetch_secaudit.sh -b https://<your-mirror>/secreview -d /opt/oninit
-v VERSION picks a release (default 1.3), -n NETRC supplies credentials
for a protected location, and -k keeps a failed download, renamed
.unverified, for inspection.
4. What you get
Everything is written to the output directory, and bundled as a .tar.gz beside it.
| Path | Contents |
|---|---|
findings.csv | One row per check per object: id,severity,status,object,detail. Load it into a tracker or a report. |
summary.txt | Counts by status and severity, and every Critical or High failure. |
evidence/ | The raw output behind each finding: onstat and onaudit output, sqlhosts, the onconfig, trust files, and one unload file per catalog query. |
Status is one of PASS, FAIL, WARN
(needs judgement), MANUAL (evidence collected, a person decides), NA
(does not apply to this version or configuration) or ERROR (could not collect).
Severity is Critical, High, Medium,
Low or Info.
The format of a row, with a made-up value for illustration:
CFG-04,Medium,FAIL,"UNSECURE_ONSTAT","Set to 1: any OS user can see session SQL"
Every id is a stable check ID (CFG- for onconfig,
OS- for installation and file security, NET- for listeners,
AUTH- for authentication, PRIV- for privileges,
EXT- for UDRs, SPL and session hooks, DATA- for data at rest
and backups, AUD- for auditing, ER- for Enterprise Replication, HA- for replication and
high availability, VER- for support and patch level), so a
row in the CSV maps straight to its rationale and remediation in the checklist.
5. Retesting
After remediation, run the script again with the same options. The difference
between the two findings.csv files is the retest evidence:
diff before/findings.csv after/findings.csv
6. Known limits
- Release 1.2 was run read-only against one live Informix 14.10.FC13W7
instance and against a mock instance. The Enterprise Replication checks
(
ER-) have not yet run against a live replication topology, so check those rows against the evidence. - Every command capture is limited to 1 MiB and no file the script writes can
exceed 512 MiB; a truncated capture ends with a
[truncated by ifx_secauditline. EXT-04skips the built-in routines by their routine id (558 is the highest on 14.10, checked on 14.10.FC13W7). On other releases it also lists built-in routines and says so.- The
EXT-03check forSYSTEMin SPL is a text match onsysprocbody; comments and split lines can cause false positives or misses. - High-availability detection reads
onstat -g driandonstat -g cluster; Enterprise Replication is detected separately fromsyscdrandcdr list server. - The support and fix-level check (
VER-02) knows the 14.10.xC13 and CVE-2026-13476 levels. Later bulletins need a manual check until the table in the script is updated. - Windows instances are not supported.
The output describes how to attack the system it came from. Store it outside any served directory and out of public repositories, and never put passwords, keys or keystores in a report: record where a secret lives, not its value.