FI Finnish
SE Swedish
FR French
PL Polish
DE German
US English (US)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

English (US)
FI Finnish
SE Swedish
FR French
PL Polish
DE German
US English (US)
  • Log in
  • Home
  • Platform
  • ESM
  • ESM Admin Manual
  • Security and Compliance

Security Logs and Settings

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Service Management
    Matrix42 Professional Solution Matrix42 Core Solution Enterprise Service Management Matrix42 Intelligence
  • Identity Governance and Administration (IGA)
    IGA overview IGA solution library
  • Platform
    ESM ESS2 ESS Efecte Chat for Service Management Integrations Add-ons
  • Release Notes for M42 Professional, IGA, Conversational AI
    2026.1 2025.3 2025.2 2025.1 2024.2 2024.1 2023.4 2023.3 2023.2 2023.1 2022.4 2022.3 Release Information and Policies
  • Other Material
    Terms & Documentation Guidelines Accessibility Statements
  • Services
+ More
    • Service Management

    • Identity Governance and Administration (IGA)

    • Platform

    • Release Notes for M42 Professional, IGA, Conversational AI

    • Other Material

    • Services

Security Logs and Settings

Security Logs

ESM creates two types of security logs: security log and configuration log. These logs record important configuration changes, which may affect the security of the application for example by changing permissions or authentication settings. Both logs store the time and type of the change and user who executed the action.

Logs are created by Log4j library and can be customized using webapp\WEB-INF\custom-log.properties file. If file doesn't exists then webapp\WEB-INF\classes\custom-log.properties is used, but it will be overridden on each update. To customize log location user must add JVM parameter efecte.logs.path="...".

Default location for security logs are:

  • for Windows installations: EFECTE_INSTALLATION_DIR\log
  • for Linux installations: EFECTE_INSTALLATION_DIR\tomcat\log

Logs are divided into two separate files:

  • efecte_configuration.log
  • efecte_security.log

Security Log

Security log logs the following events:

  • Logins with a local account (who, when, where from [IP])
  • Failed login attempts with a local account
  • Logouts with a local account
  • Successful AND failed changes on User “security settings”
    • User level changes
    • Authentication method
    • Password
    • Username
  • User permission changes
    • user given a role
    • removed a role
  •  Creating a role
  •  Deleting a role
  •  Creating a user  
  • Deleting a user
  • Giving a module permission to a role (write, read-only, none)
  • Removing a module permission from a role
  • Giving an administrative permission to a role
  • Removing an administrative permission from a role
  • Editing Search and user interface settings of a role
  • Deleting a user folder (causes role & user deletion)
  • Creating a user folder
  • Changes in EUP configuration of a template (log the EUP path, old and new)

Configuration Log

Configuration log logs the following events:

  • Deleting a template
  • Deleting an attribute (affects these templates / classes)
  • Adding a template
  • Adding an attribute (affects these templates / classes)
  • Deleting a folder
  • Adding a folder
  • Deleting a group/class (affects these templates / classes)
  • Adding a group/class (affects these templates / classes)
  • Adding an attribute to a group/class (affects these templates / classes)
  • Removing an attribute from a group/class (affects these templates / classes)
  • Adding a group/class to a template (affects these templates / classes)
  • Removing a group/class from a template (affects these templates / classes)

Local Password Strength

It’s possible to define length and other requirements for local passwords (stored in Efecte Service Management database).

Platform setting password.rule.regexp contains the configuration as a regular expression.

Note:

Default password requirement is: at least 8 characters long and contain at least an uppercase character, and at least one number.

 

 

safety journals protection records esm admin local password strenght security logs configuration log security log

Was this article helpful?

Yes
No
Give feedback about this article

Table of Contents

Related Articles

  • ClamAV Anti-Virus
  • File Upload Security

Copyright 2026 – Matrix42 Professional.

Matrix42 homepage


Knowledge Base Software powered by Helpjuice

0
0
Expand