Native integrations utilize the published API (Application Programming Interface) or SDK (Software Development Kit) of the manufacturer to develop integration between 2 systems. These published API/SDKs provide a way for third-party developers to properly interact with their systems.
The benefit of utilizing a native integration is it often provides the ability to access a richer set of functions on the integrated system. At SureView, we have found that syncing data between two systems is one of the most powerful capabilities of native integrations. This is especially important in large organizations where there is constant change—new builds and upgrades mean that the cameras, doors, and security devices are constantly being added or changed. Managing these changes is time-consuming and can be fraught with human error. Automating these processes through integration delivers a large number of operational benefits.
Things to look out for
The downside to native integrations is that there are no defined standards or approaches to developing or maintaining APIs or SDKs. It is entirely dependent on the openness and commitment of the manufacturer. As such, some API/SDKs are well architected, documented, maintained, and supported, while others are not. A common way to address this is a certification process, whereby the manufacturer certifies an integration with the third-party system. This provides customers with confidence that both manufacturers have a relationship and have jointly reviewed the integration to ensure it meets their collective best practices. Not every manufacturer has a certification process, so check with both vendors to establish the status and supported features of the integration.
Read more in our full whitepaper, Integrating Your Security Operation: A Roadmap For Connecting Technology to Deliver Optimum Operational Value.