Certificate authority
A certificate authority (CA) is an entity responsible for issuing and signing public key certificates under a defined policy, and for revoking them when appropriate.
Issuing a certificate does not make everyone trust it
A CA signs a certificate that connects a public key to information about its subject. The application checking that certificate still needs to decide whether it trusts the issuer and accepts the certificate for the intended use.
In an X.509 deployment, the issuer may be an intermediate CA whose certificate chains toward a trust anchor. The trust anchor is the trusted key and associated information used as the starting point for validation. It is often distributed as a root certificate. The CA issues the certificate; the trust anchor is where the checking system starts its trust decision.
Adding trust is a configuration change
Installing an additional root certificate can change which certificates a device or application will accept. That deserves a clear purpose and an authorized owner. The certificate’s display name does not establish who approved that change.
Apple illustrates why the deployment route matters. On iOS, iPadOS, and visionOS, a certificate in a manually installed profile is not automatically trusted for SSL/TLS; Apple documents different trust behavior for certificates deployed through Configurator or device management.
The configuration profile article explains how to review the requested trust change. A certificate that validates successfully still does not prove that a message, software download, or business instruction is benign.