The logging of configuration data changes is not activated for the tables listed below. This does not present an actual security problem in the sense that it enables or prevents attacks. However, for security reasons, it is useful to log configuration data changes to meet audit requirements and to retain any information that may be required for reconstructing an attack.

Archiving:
SXMSARCITF
SXMSARCITF2 (higher than NetWeaver Release 6.40)

General Integration Engine configuration:
SXMSCONFPP
SXMSDCONF
SXMSINTERFACE
SXMSJOBS
SXMSMSGDEF

Message packaging:
SXMS_BCFG_MAST (higher than NetWeaver Release 6.40)
SXMS_BCFG_MATT (higher than NetWeaver Release 6.40)
SXMS_BCONF (higher than NetWeaver Release 6.40)
SXMS_BCONF_SPEC (higher than NetWeaver Release 6.40)

EOIO queue reorganization:
SXMS_EOIO_STAT (higher than NetWeaver Release 6.40)

User-defined search:
SXMS_LMS_EXTR (higher than NetWeaver Release 7.01) (higher than NetWeaver Release 7.10)
SXMS_NSPREFIX (higher than NetWeaver Release 7.01) (higher than NetWeaver Release 7.10)
SXMS_EXT_FIL (higher than NetWeaver Release 7.01) (higher than NetWeaver Release 7.10)

WS adapter:
SXMS_WS_SYSERR (NetWeaver Release 7.10 or higher)
SXMS_WS_SYSERSAP (NetWeaver Release 7.10 or higher)

This means that you can track activities in the content of these tables (for example, the update or deletion of existing entries).
Note that changes are recorded only if the profile parameter rec/client is set.