Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

INDEX

Documentation Library

Search for information on Hornbill Documentation.

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?

What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Penetration Tests

Every change either in code or infrastructure is reviewed to ensure that it poses no change to the overall integrity and security of the Hornbill platform. These changes are tested via automated testing on every commit and build against a suite of tools\tests (over 10,000 individual API tests alone and counting) and any issues addressed before promoting out of the development environments. Hornbill also performs monthly external scans of all end points using industry approved tools to ensure nothing has been missed. We then, on an annual basis, have an external company perform a full penetration test on the entire platform to validate our results. Full penetration reports are available on request.

External Penetration Tests

As per Section 3.4.3 of Contract , Hornbill does not allow external 3rd party penetration tests on our live services. Whilst we are confident that nothing will be found (We already have an external penetration performed annually with all issues addressed - Report available on request) there are several reasons for this. These include, that being a shared service with common front ends, any unexpected or incomplete access will flagged by security measures\threat detection by our front end\services\monitoring automatically which may cause unwanted downtime\blacklisting IPs against the given instance or others, the source IP or range may be shared and in blocking a perceived attacked we could end up blocking valid requests. Penetration tests can also be load heavy due to the automatic tools\scanners used which may impact performance for customers on any shared resources or cause rate limiting. Automatic actions may be outside of Hornbill control (For example in case of testing against logins with an account tied to SAML\Google etc) which may impact delivery of our services. There is also the question of what a non-directed or blanket test would find, given the complexity of the system and front end servers screening requests.

We would therefore strongly recommend that any customer wishing to perform an external penetration test contact security@live.hornbill.com to obtain a copy of the latest penetration tests (External and Internal) and allow us to discuss your goals with an aim to finding a solution.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document