Common use of Input Control Clause in Contracts

Input Control. Detection: Intentive designed its infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregated log data and alert appropriate employees of malicious, unintended, or anomalous activities. Intentive personnel, including security, operations, and support personnel, are responsive to known incidents. Response and tracking: Intentive maintains a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, Intentive will take appropriate steps to minimize product and Customer damage or unauthorized disclosure. Communication: If Intentive becomes aware of unlawful access to Customer data stored within its products, Intentive will: 1) notify the affected Customers of the incident; 2) provide a description of the steps Intentive is taking to resolve the incident; and 3) provide status updates to the Customer contact, as Intentive deems necessary. Notification(s) of incidents, if any, will be delivered to one or more of the Customer’s contacts in a form Intentive selects, which may include via email or telephone.

Input Control. Detection: Intentive Insycle designed its infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregated log data and alert appropriate employees of malicious, unintended, or anomalous activities. Intentive Insycle personnel, including security, operations, and support personnel, are responsive to known incidents. Response and tracking: Intentive Insycle maintains a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, Intentive Insycle will take appropriate steps to minimize product and Customer damage or unauthorized disclosure. Communication: If Intentive Insycle becomes aware of unlawful access to Customer data stored within its products, Intentive Insycle will: 1) notify the affected Customers of the incident; 2) provide a description of the steps Intentive Insycle is taking to resolve the incident; and 3) provide status updates to the Customer contact, as Intentive Insycle deems necessary. Notification(s) of incidents, if any, will be delivered to one or more of the Customer’s contacts in a form Intentive Insycle selects, which may include via email or telephone.

Input Control. Detection: Intentive Keeper Security designed its infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregated log data and alert appropriate employees of malicious, unintended, or anomalous activities. Intentive Keeper Security personnel, including security, operations, and support personnel, are responsive to known incidents. Response and tracking: Intentive Keeper Security maintains a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, Intentive Keeper Security will take appropriate steps to minimize product and Customer damage or unauthorized disclosure. Communication: If Intentive Keeper Security becomes aware of unlawful access to Customer data stored within its products, Intentive Keeper Security will: 1) notify the affected Customers of the incident; 2) provide a description of the steps Intentive Keeper Security is taking to resolve the incident; and 3) provide status updates to the Customer contact, as Intentive Keeper Security deems necessary. Notification(s) of incidents, if any, will be delivered to one or more of the Customer’s contacts in a form Intentive Keeper Security selects, which may include via email or telephone.

Input Control. Detection: Intentive Applozic designed its infrastructure to log extensive information about the system behavior, traffic received, system authentication, and other application requests. Internal systems aggregated log data and alert appropriate employees of malicious, unintended, or anomalous activities. Intentive Applozic personnel, including security, operations, and support personnel, are responsive to known incidents. Response and tracking: Intentive Applozic maintains a record of known security incidents that includes description, dates and times of relevant activities, and incident disposition. Suspected and confirmed security incidents are investigated by security, operations, or support personnel; and appropriate resolution steps are identified and documented. For any confirmed incidents, Intentive Applozic will take appropriate steps to minimize product and Customer damage or unauthorized disclosure. Communication: If Intentive Applozic becomes aware of unlawful access to Customer data stored within its products, Intentive Applozic will: 1) notify the affected Customers of the incident; 2) provide a description of the steps Intentive Applozic is taking to resolve the incident; and 3) provide status updates to the Customer contact, as Intentive Applozic deems necessary. Notification(s) of incidents, if any, will be delivered to one or more of the Customer’s contacts in a form Intentive Applozic selects, which may include via email or telephone.