unconfined_service

Hi Team,

While doing Nessus scan in one the host we see most the DB services are showing as (unconfined_service_t) as below along with other service. What is the reason for this and is there anyway we can remediate these. Is there any harm if it is run as "unconfined_service_t". Please help me to understand.

[root@localhost ~]# ps -eZ | grep unconfined_service_t
system_u:system_r:unconfined_service_t:s0 1153264 ? 00:12:43 beam.smp
system_u:system_r:unconfined_service_t:s0 1153302 ? 00:00:00 erl_child_setup
system_u:system_r:unconfined_service_t:s0 1153348 ? 00:00:11 gosecrets
system_u:system_r:unconfined_service_t:s0 1153353 ? 07:09:36 beam.smp
system_u:system_r:unconfined_service_t:s0 1153378 ? 00:00:00 erl_child_setup
system_u:system_r:unconfined_service_t:s0 1154335 ? 00:22:41 beam.smp
system_u:system_r:unconfined_service_t:s0 1154344 ? 00:00:00 erl_child_setup
system_u:system_r:unconfined_service_t:s0 1154398 ? 00:00:01 goport
system_u:system_r:unconfined_service_t:s0 1154402 ? 00:55:42 prometheus
system_u:system_r:unconfined_service_t:s0 1154414 ? 00:02:37 goport
system_u:system_r:unconfined_service_t:s0 1154419 ? 00:26:37 goxdcr
system_u:system_r:unconfined_service_t:s0 1155676 ? 00:02:30 goport
system_u:system_r:unconfined_service_t:s0 1155681 ? 01:40:34 indexer
system_u:system_r:unconfined_service_t:s0 1155696 ? 00:00:50 goport
system_u:system_r:unconfined_service_t:s0 1155701 ? 00:43:24 cbq-engine

Thanks,
Debasis