Our Partners close more business.
Use these powerful resources to win more business, faster, with less effort.
Call 877-411-2220 x121 for personal support with any opportunity.
RESET SEARCH
Hosting Quote Estimator
GET a FREE Sandbox or Trial Environment NOW
How To Use This Tool:
To find answers to common RFP and RFI questions, select a tag, or, search for terms like "security", "performance", etc. You will find common questions and answers grouped together in one record. Follow the tag links to refine your search. Supporting downloads and documentation are available, below.
Please login to obtain download access to additional supporting documentation. Registered users can also contribute to the database. You can request access by Contacting Us.
Supporting Documents
Please note that assets with generic thumbnail require login for access. If you require access please Contact Us.
© Omegabit LLC, 2023
Enter a Search Phrase or Select a Tag
Content with tag incident handling .
Security Incident Handling
Q:
Do you have documented incident response policy and procedures?
Are personnel defined with roles and responsibilities in incident response plan and trained at least annually?
Do you have an automated mechanism to increase the availability of incident response-related information and support?
Do you conduct incident response tests/exercises with all appropriate parties at least annually and revise the plans to address changes and problems encountered?
Do your incident response tests include other related plans (e.g. BC or DR Plans, Crisis Communication Plans, Critical Infrastructure Plans and etc.)?
Do your incident response tests include other related plans (e.g. BC or DR Plans, Crisis Communication Plans, Critical Infrastructure Plans and etc.)?
Do you employ automated mechanisms to support incident handling processes that include preparation detection, analysis, containment, eradication, and recovery?
Are incident handling processes incorporated into contingency planning activities?
Do you incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises, and implement the resulting changes accordingly?
A:
ref: Omegabit IT Security TOC
Yes
This question is vague; however, we do provide means of escalation and the dissemination of information with backup strategies in case of critical failure.
Yes
Yes
Yes
Yes
Yes
Security Incident - reporting and notification
Q:
Do you track, analyze and report on all security incidents?
Yes; varies by method of detection but, is typically automated by email and status dashboard notification. Severe or high-risk conditions engage a human chain of response protocol. Critical systems are monitored redundancy by multiple means and pathways. Escalations are programmed to trigger alerts via alternate channels if not acknowledged. These methods and alerts are similar regardless of trigger source (typical instability or application issue vs. targeted security incident or malicous attack); any source of instabilty or threat is responded to with high priority. Depending on incident type and level of escalation, it may be flagged for investigation and a trouble ticket opened for further investigation. Any incident of substance is documented with visibilty by the Client; proactive notifications are sent for incidents of immediate concern or requiring action or where a breach has occured.
A:
Omegabit maintains a comprehensive and proprietary database for the purposes of troubleshooting and documenting known incidents and actions, which is utilized to inform resolution path options and document outcomes for all parties.
As it relates to customer communications, Omegabit notifies Client designated contacts of urgent incidences by email, and telephone wherever practical, as well as a shared ticketing system to track the incident response.
Severe or high-risk conditions trigger a human-managed chain of response protocol. Critical systems are monitored automatically by multiple. Escalations are programmed to trigger alerts via alternate channels if not acknowledged. Depending on incident type and level of escalation, it may be flagged for more investigation and a trouble ticket opened for further analysis. Any incident of substance is documented with visibility by the Client; proactive notifications are sent for incidents of immediate concern or requiring action or where a breach has occurred.
Notification follows the SLA terms and conventional practice.
Please refer to the Omegabit IT Security TOC for more information.