Difference between revisions of "ISO:Operations"

From Hornbill
Jump to navigation Jump to search
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
This document can now be found at its new location in the [https://docs.hornbill.com/hornbill-cloud/iso/operations/ Hornbill Document Library].
 +
 +
[[file:hornbill-document-library.png|ISO Operations|link=https://docs.hornbill.com/hornbill-cloud/iso/operations/]]
 +
 +
<!--
 
==Capacity management==
 
==Capacity management==
 
 
Line 21: Line 26:
 
* Sanity (Checks for Mail Queues, Expected load etc).
 
* Sanity (Checks for Mail Queues, Expected load etc).
 
* SIEM (APIs\Resource Usuage\Network Traffic and DB Access\Requests)
 
* SIEM (APIs\Resource Usuage\Network Traffic and DB Access\Requests)
 +
 +
 +
Hornbill also maintains a fingerprint for each instance for each hour of the day across different days for key metrics (APIs\Resource Usage\Network Traffic\DB Access\Count of Emails In\Out etc) which are compared with the live instance metrics every 15 minute. This allows us to detect any abnormal patterns which may indicate internal issues, threats, security issues, misconfiguration or other strangeness near realtime. Anything outside of a standard deviation from normal for 1 or more the key metrics for each fingerprint is subjected to further automatic review and the outcome of this will escalate under conditions to the Cloud Team. After review this may be escalated to the instance contacts for clarification or notification of possible issues. In extreme circumstances (Either exceptional load, possible security issue or similar) Hornbill will act to prevent harm to the instance or platform and the contact for instance informed of the action taken and reason.
  
 
==Backups ==
 
==Backups ==
Line 48: Line 56:
  
 
==Access==
 
==Access==
All Logins to systems processing customer data will automatically send a report to the Hornbill Audit Logs mailbox. This Login must then be associated with a given service manager request or Hornbill workspace post via Cloud Login Audit catalogue item to ensure a valid reason exists to login. These Logins are then audited by the Security manager to ensure no unauthorised access was performed.  
+
Access to any system is restricted. All default passwords are changed. All Logins to systems processing customer data will automatically send a report to the Hornbill Login Workspace (allows anyone in company to highlight or ask questions on why access and provides transparency) and raises a request. This Login must then be associated with a given service manager request or Hornbill workspace post to ensure a valid reason exists to login. These Logins are then audited by the Security manager to ensure no unauthorised access was performed.  
  
 +
Passwords on all systems are changed on leaver or schedule.
  
 
Backups are restored (and therefore restore process tested) nightly to ZIP before being pushed to offsite location and a random backup restore is performed on schedule basis to ensure that backups are correct\valid.
 
Backups are restored (and therefore restore process tested) nightly to ZIP before being pushed to offsite location and a random backup restore is performed on schedule basis to ensure that backups are correct\valid.
Line 79: Line 88:
 
== Hardware ==
 
== Hardware ==
 
Only hardware provided by the IT team and obtained via existing approved vendors may be used to access the management or customer networks. All Clocks are syncronized with NTP and checked to be within 1 minute of primary servers. All default passwords changed. All hardening is inline with Vendor, Industry and Hornbills own polices\standards. All hardening is confirmed via monitoring and any changes would automatically escalated and automatically reverted within 5 minutes of any unsanctioned change.
 
Only hardware provided by the IT team and obtained via existing approved vendors may be used to access the management or customer networks. All Clocks are syncronized with NTP and checked to be within 1 minute of primary servers. All default passwords changed. All hardening is inline with Vendor, Industry and Hornbills own polices\standards. All hardening is confirmed via monitoring and any changes would automatically escalated and automatically reverted within 5 minutes of any unsanctioned change.
 +
 +
-->
 +
<!-- hornbill-cloud/iso/operations -->
 +
[[Category:HDOC]]

Latest revision as of 19:56, 11 April 2024

This document can now be found at its new location in the Hornbill Document Library.

ISO Operations