This read-only Counter32 counts incoming messages dropped because the security level asserted by the underlying transport model (e.g. TLS or SSH) was lower than what the requesting application required. Admins use it to spot misconfigurations where a transport isn't providing the encryption/authentication strength an application expects. For example, an admin seeing this counter climb might discover a client connecting over an unauthenticated transport when the manager requires authPriv-equivalent security.