|
SOLICITATION # CH16012
<br />- Log files, represented by the EventType field, are only generated if there is at least one event of
<br />that type for the day. If no events took place, the file won't be generated for that day
<br />- Log files are available based on CreatedDate for the last 30 days when organizations purchase
<br />User Event Monitoring or one day for Developer Edition organizations.
<br />Businesses desire certainty that their data is accurate, complete and reliable, enabling them to
<br />meet stringent industry regulations. With Field Audit Trail, customers can track changes at the field
<br />level for up to ten years and set different policies for each Salesforce object to ensure data is
<br />purged when no longer needed. Life sciences companies running clinical trials in Salesforce, for
<br />example, can now maintain a complete audit trail of patient data so they can safeguard the
<br />integrity of clinical trial results and comply with FDA regulations.
<br />- All event monitoring logs are exposed to the API through the EventLogFile object, however there
<br />is no access through the user interface.
<br />Event monitoring can be used with 28 different file types:
<br />Apex Callout, Apex Execution, Apex SOAP, Apex Trigger, API, Async Report, Bulk API, Change
<br />Set Operation, Content Distribution, Content Document Link, Content Transfer, Dashboard,
<br />Document Attachment Downloads, Login, Login As, Logout, MDAPI Operation, Multiblock Report,
<br />Package Install, Report, Report Export, REST API, Salesforce1, Adoption (UI Tracking), Sandbox,
<br />Sites, Time -Based Workflow, URI, Visualforce.
<br />Event Monitoring Transaction Security
<br />Transaction Security policies give your Agency a way to look through events in your organization
<br />and specify actions to take when certain combinations occur. A transaction security policy consists
<br />of events, notifications, and actions. Transaction Security monitors events according to the policies
<br />that your Agency sets up. When a policy is triggered, you can receive a notification and have an
<br />optional action taken.
<br />For example, suppose that you activate a policy to limit the number of concurrent sessions per
<br />user to three. A user with three login sessions tries to create a fourth session. Your Agency can
<br />require a user to end one of their existing sessions before proceeding with the new session. At the
<br />same time, you are notified that the policy was triggered.
<br />ServiceNow The ServiceNow application writes detailed log information that is stored in tables within a
<br />customer's instance. As this is customer data in a customer's instance, ServiceNow does not
<br />attempt to monitor or view this data unless specifically requested by a customer. As a result the
<br />customer is responsible for monitoring the contents of these logs files. The log data is protected in
<br />the same manner as all other customer data. Event logs can also be configured to feed into a
<br />customer's environment via ServiceNow's Syslog probe allowing the logs to be stored within the
<br />customer's environment in a syslog repository or SIEM and retained according to the customer's
<br />requirements.
<br />ServiceNow's application logging includes verbose transaction logs, these logs are retained within
<br />the instance for 30 days. Event logs are stored for seven days and audit histories are retained
<br />indefinitely in the instance.
<br />Transaction logs represent every click, view, and system event that occurs in an instance and as a
<br />result, will grow very large, quickly. They provide a level of detail that is frequently used for
<br />troubleshooting issues with an instance. They can also provide detailed intelligence on the
<br />behaviors within an instance. These logs can be downloaded to customers' environments, if they
<br />need to be retained for longer than 30 days.
<br />The event logs on the other hand are less granular; they will include the creation of an incident, or
<br />deletion of problem, or any one of the 250 standard events. They may also contain customer
<br />carahsoft 74 carahsoft
<br />
|