Q: 1
A common drawback of email software packages that provide native encryption of messages is that
the encryption:
Options
Discussion
I don’t think it’s D. B is the issue, since proprietary encryption can't talk across platforms.
C vs D. If we’re talking about actual crypto strength limitations, I’d say C is also super common with older packages.
Sick of these "interoperability" questions, but yeah, B is right. Different email clients rarely play nice together with built-in encryption. Seen similar on other practice sets, so pretty sure that's what ISACA wants here.
Had something like this in a mock. B makes sense since each encryption method works fine inside its own platform, but you always hit issues when you try to send encrypted mail between different email software. Pretty sure that's what they're looking for here.
B , native encryption always falls over when you mix different email products.
Option B for me. Native encryption just doesn't play nice between different email software, so users end up locked in or unable to exchange secure emails. I think this is the most common pain, not key recovery or attachment issues. Makes sense?
A is wrong, B. Interoperability trips up native encryption unless both sides use matching software, which isn’t always the case with cross-vendor emails.
I don't think it's D. B makes more sense since lack of interoperability is a constant headache with native email encryption, especially if sender and receiver use different vendors. D is more about compliance rather than being a "common" issue. Disagree?
Why wouldn't A be right? Haven't seen native email apps struggle as much with attachments as with cross-platform issues.
D imo
Be respectful. No spam.
Question 1 of 35