Question: What is the additional step taken when revoking a TLS CA cross-certificate that is not required for revoking a SEG CA cross-certificate?
Option 1: Adding the cross-certificate to the Interconnection CA's CRL
Option 2: Removing the cross-certificate from the Interconnection CA's CR
Option 3: Updating the TLS entity's configuration to prevent future use
Option 4: Deleting the locally stored cross-certificates in the TLS entities
Explanation: The key difference in revocation procedures between SEG CA and TLS CA cross-certificates lies in how they are stored. For TLS CA cross-certificates stored locally within TLS entities, an additional step of deleting these local copies is necessary upon revocation. This ensures consistency across all storage locations, enhancing security by preventing potential misuse of the revoked certificate. In contrast, SEG CA cross-certificates do not require this extra step as their storage and management are centralized, covered by steps common to both types.