Update wording and mappings for logging requirement

#### 5.2.X.x **MI-LOGG**: Logging

The product shall record log messages indicating security-relevant internal events in an internal or external log. The log messages shall not include any confidential information such as PII, secrets, or credentials, or any information which might reasonably be expected to include such items.

The product shall record log messages indicating security-relevant internal events in an internal log or transmit them to the host system logging system. The log messages shall not include any confidential information such as PII, secrets, or credentials, or any information which might reasonably be expected to include such items.

  * Reference: TR-LOGG

  * Objective: Monitoring and recording security-relevant events

Guidance: One type of event whose log message must take care to not accidentally include a secret is failed password authentication attempts. Since people often type their password into the username field, including the username field in the log message may result in including a secret in the log message.

| Risk factors                          | Requires mitigations |

|-------------------------------------------------|----------------------|

| SFT < 1 & SDS < 1 & FUN < 1 & SYS < 1 & NET < 1 | none                 |

|---------------------------------------|----------------------|

| max(PHY, SFT, NET, SDS, SYS, FUN) < 1 | none                 |

| all others                            | LOGG                 |

| Security Profile | Requires mitigations |

|------------------|----------------------|

| FIXME            | none                 |

| all others       | LOGG                 |

> FIXME: Update when risk factors are updated

| any              | LOGG                 |

### 5.2.X **TR-SCDL**: Secure deletion