1 of 9

Requirements for improved LN Auditing

Marek Jansa

Senior Business Analyst for LN Technology

Infor LN Cloud Edition

INDUSTRIAL MANUFACTURING

Bram Vijfhuizen

Senior Product Manager for LN Technology

1

2 of 9

Agenda

Audit configuration

Database-related trail
Special events trail

Retention Policy, Egress, Metrics
Querying
Reading the audit

2

3 of 9

Audit configuration – database-related trail�Tracking of activity related to changing / reading DB data

Table-oriented configuration

Current functionality

Select tables and fields

Create company groups

Create audit profiles

New functionality

Audit BLOB fields (Extensions, Report Personalizations)
Use conditions
Simple: If [field] [operator] [value] then audit or not audit.
Complex: Using programming language and return(true|false) logic.

User/Role-oriented configuration

Track activity of

A user
A group of users
All super users
Users assigned a specific Role

Changes X Everything configurable per User

API-oriented configuration

Track activity of

A specific REST API

All above configuration types

Select detail of trail:

Only Changes
Everything [Changes + Reads]

3

4 of 9

Audit configuration – special events trail�Tracking of activity related to writing files or activating processes

Change files and Actions

Tracking actions in sessions, e.g.:

Convert to runtime
Compile object
Change CPQ model

Configuration

Track an action from LN session
Track the folders visible in File Manager

Detail

Actions: Who triggered an action
Files: Changes only
Files: Changes and reads

Processes

Track who (or which API) started or stopped a process, e.g.

DOM engine
Archiving engine
DPM publishers
BOD workers
Tenant status changes (Admin-only,..)
Tenant mode changes (Operational,..)

Configuration

Track a specific process

Data Definition Language

Track DDL statements

CREATE TABLE
ALTER TABLE
DROP TABLE

Configuration

Package / Module / Table level
Company level

4

5 of 9

Audit configuration – sync content between tenants

Import / Export capabilities

Export/Import audit profiles:

As Configuration Object / Local Packages
As a file to be copied from one env to another

Global Packages

Import standard audit content
As well for queries (slide 7)

5

6 of 9

Retention policy, egress and metrics

Retention policy

Define a period after which to

Delete the audit trail
Egress the audit trail
Delete the egressed audit trail

Configuration

Per audit category

Egress

Audit trail is moved to a frozen storage with lower costs

The data will be offloaded based on the retention policy and won’t be available for querying.
A request must be registered to download the egressed audit trail back to LN based on a defined time range.
The time between the request and the availability of the data back in LN would be max 24 hours.
There will be a limit of how much data can be moved back from egress to online at once.

Metrics

It should be visible how much storage is occupied by the LN audit trail

In the online database
In the egressed storage

6

7 of 9

Querying

Flexible queries

To achieve enough flexibility, customers should have a selection of filters they could use solely to print a large list of transactions or combine a number of various filters together and receive a very specific result.

These filters, that should be correlate-able are of the following types:

table filters (including company number, field value conditions)
user filters (including user type [normal | super], user name)
origin filters (transactions committed by a job, by user, by API, including the name of the API or the job, by a session (GTM))
time filters (range of timestamps)
event (a list of special events)

Human-readable language

The queries can be constructed

using session capabilities (WYSIWYG)
manually (code text editor)

Session (wysiwyg) queries

using intuitive UI screens
drop-down options
zoom-fields
result is a human-readable query text

Text queries

the queries generated by the session can be reused
when manually editing, the query is validated
switch between text view / session view: validated text query will result in changed fields in the UI

Query storage

Users should be able to store the queries and

duplicate them,
edit them,
delete them,
import and export from one environment to another

APIs

Users should be able use APIs to query the audit.

to automate business

7

8 of 9

Reading the query output

Different formats

The users should get multiple options for getting the query output:

XLSX / CSV (Spreadsheet)
JSON
Generated PDF 4GL reports

Protection / Verification

Any output format should support at least one layer of optional protection and/or verification:

Signature for PDF
Password protection for XLSX
Encryption for JSON

Scheduled reports

Register a query with a required result format and schedule it to be generated based on a schedule:

Send to email
Store as a file
Send as a BOD
Send to AI for processing / forecast
[possibly] Send to GRC / Data Fabric

8

9 of 9

Marek Jansa

Senior Business Analyst

marek.jansa@infor.com

9