'content checking' is to verify that no secrets are included in anything sent somewhere unapproved. For example, banks and other fiduciaries need to ensure that private financial data isn't released, educational institutions need to ensure that educational data isn't released, and so on.
It is an integral part of security for an organization -- it's what makes trade secrets secret (if the corporation doesn't do its part to keep it secret, there's no secret to consider trespassed upon), and it ensures that its legal obligations are maintained. It's also necessary to comply with a couple of federal court rules regarding discovery. -Kyle H 2008/11/18 Graham Leggett <[EMAIL PROTECTED]>: > Anders Rundgren wrote: > >>> There is no such thing as secure email at the server level. >> >> For an *organization* this is statement is principally wrong. For an >> organization the server is the only place where you actually can perform >> security operations including content checking in a cost-efficient way. >> That is, >> S/MIME encryption poorly addresses the needs of organizations while it is >> much too hard to use for consumers. > > What is "content checking" and what does it have to do with security? > > Regards, > Graham > -- > > _______________________________________________ > dev-tech-crypto mailing list > dev-tech-crypto@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-crypto > > _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
