- From: Joseph Hui <Joseph.Hui@exodus.net>
- Date: Thu, 25 Jul 2002 18:46:53 -0700
- To: "Prafullchandra, Hemma" <hprafullchandra@verisign.com>, <www-ws-arch@w3.org>
- Message-ID: <45258A4365C6B24A9832BFE224837D551D1CE5@SJDCEX01.int.exodus.net>
Thanks again, Hemma. I'm also noting your A+B as Text B embellished. If the similarity shared by yours and Hoa's is also shared by popular sentiment, then I think we're just aboutt there. Joe Hui Exodus, a Cable & Wireless service =================================== -----Original Message----- From: Prafullchandra, Hemma [mailto:hprafullchandra@verisign.com] Sent: Thursday, July 25, 2002 6:02 PM To: www-ws-arch@w3.org Subject: RE: Glossary Definition for Audit(ing) [Was: RE: AG004 Closure S ought] Text A: Auditing provides passive tracking and logging of security-related activities, incidents, and events (such as authentication events, unproven claims, or bad signature occurrences). Administrator can securely managed and analyze these audit records to take appropriate action against antagonists. Text B: Audit: A service that reliably records security-related events for future reference. The resulting audit trail may be used to detect attacks, confirm compliance with policy, deter abuse of authority or other purposes. Final:A+B: Auditing: A service that reliably and securely records security-related events (such as authentication events, policy enforcement decisions, abnormal (deviations from the norm) events). The resulting audit trail may be used to detect attacks, confirm compliance with policy, deter abuse of authority or other purposes. Unless there was something specific in A, about the players involved that you wanted to capture or the nature of this activity. Feel free to polish A+B further but I really think this captures the essence of what we want to say given all the other restrictions! hemma
Received on Thursday, 25 July 2002 21:46:03 UTC