Integration - what does it mean?

Look up the definition of integrate and you'll find a broad range of explanations:

• Dictionary.com: to bring together or incorporate (parts) into a whole.
• Merriam Webster: to unite with something else.
• Cambridge Dictionary: to combine two or more things in order to become more effective.

It's this last definition, from the world's oldest publishing house (Pub Quiz Trivia - they published their first book in 1584), that sums up the intent of 'integrating' in a security context.

Just as there are many definitions for integrate and integration, so too are there a range of outcomes when systems or products are integrated. Let's explore some now.

Surface Level Integration

Disparate systems, be they door access control, locker, elevator, printing or transport, often allow the same credential to be used between them. A person may be given one mobile app that allows them access in two different buildings, despite them having completely separate systems. This certainly fits our definition of 'becoming more effective', and everything appears integrated to most users.

All too often however, an administrators time is required to manually update the details in each database as there is no communication between them. They are essentially doing the same work twice, with double the chance of error. They probably don't consider the combination very effective.

Another common surface level integration appears in elevator systems, some of which utilise completely insecure components of a swipe card when granting floor access. If you're interested, this is covered in detail here https://www.garudax.id/pulse/security-risk-exists-so-many-businesses-scares-me-brad-small/

Let's now consider some better possibilities.

Deep Integration

Consider an alternate scenario with Sarah, who has just begun a new role at technology startup Integration Incorporated. In the weeks leading up to her start date, she completed an online induction on the company's HR portal. This set in motion a chain of time and energy-saving outcomes:

• She arrives early on day one, a cold and rainy morning but the foyer door is locked. Not a problem, since the access control system was integrated with the HR database. She uses the mobile credential that was sent to her a couple of days prior to open the door.
• The receptionist, James, arrives shortly after to find Sarah waiting in the foyer. After verifying her identify, he logs on to the access control software to print her an ID badge. Since her details are already in the system, they chat over coffee while the card prints.
• James suggests that Sarah leaves her bag in a locker. The lockers are an integral aspect of the access control system, so she presents her phone and it assigns her a locker for the day.
• Sarah takes a tour of the office. She notices the room lights switch on when she uses her mobile to open doors, as the building management and access systems talk to each other.
• She learns Integration Inc. has government customers, who require a high level of security assurance. An intruder alarm is disarmed automatically when she enters her office, as the access and alarm system is one and the same.
• Day two will involve a visit to the Integration Inc's office in a shared building across town. Sarah asks James for a card to enter the building. "No need, the two buildings are synced with a secure API - what was the name of our business again?"

Taking a close look at current processes and asking if there's opportunity for a robust, secure, deep integration is worthwhile in any organisation. Secure, robust, and resilient interfaces can reduce risk, lower stress and allow people to focus on the mission instead of the technology. Feel free to reach out to me, I'm more than happy to share my experiences in this area.