A federated credential is a cloud setting that trusts an outside identity, such as a CI workflow, to get access tokens without a stored secret. Instead of keeping a long-lived key in a pipeline, the workflow presents a signed identity token from its platform, and the cloud provider exchanges it for a short-lived access token if the identity matches the configured rules.
It matters because it removes a stored secret that could be stolen. The access is temporary and tied to a specific workflow, so a leak of the token has a short useful life.
The security depends on how strictly the trust is defined. If the rules accept too many repositories, branches or workflows, an attacker who controls one of them could gain access. The setup and the names of the feature differ between providers, and a configuration that works can still be too permissive.
When using it, restrict the accepted issuer, repository, branch and environment as narrowly as possible, give the resulting role only the permissions it needs and test that an unintended workflow is refused.