Quite often, this kind of information is specific to a given table, and not directly related to any Entity. Indirectly related, yes, since often an entity maps into a table. If it is the case that you'd want one of these logging records on any table, regardless of why the table is there, then it wouldn't make much sense to have it at a conceptual level.
However, if your goal REALLY IS to represent this logging information at a conceptual level, and to do it uniformly in many places, here is a potential way to do it.
Introduce an entity for this logging information, and attach the elements you wish included, with a spanning uniqueness constraint across all of them as the primary identifier. You'll only need this shown once in the model. Then, wherever you come across an entity that you wish to have logging information, connect it to that logging information in the diagram. When it is mapped to a relational view,all of the elements you've got the primary identifier spanning for the logging information will be included, without having to repeat them on the diagram each and every time.