Are you really, really sure you want to add that third-party app?
Perhaps your hospitality business has been crying out for a new member management platform or guest check-in system. Or a rewards program or marketing platform. And your board and other business stakeholders agree that a new solution, once integrated into your environment, would give you a competitive edge.
The good news is you’ve found a solution that ticks all your boxes. Eager to start reaping the benefits, you’ve quickly signed on the dotted line, and the deal is done and dusted.
We get it. The software promises to solve many problems. It should improve operational speed, accuracy, efficiency, transparency and everything else you’ve been struggling with.
The problem is it may also pose a security risk to your business.
No one likes surprises (and often with good reason)
To improve how they do business, our clients often invest in new software. And that’s great; we’re all in favour of them evolving their operations. It does get a bit awkward, though, when they don’t mention it to us until after the contracts are signed and payments are made.
At which point, we’re asked to implement the solution regardless of the security, compliance, API and integration implications. Worryingly, these issues haven’t always been fully assessed, if they’ve been assessed at all, before the contract is signed.
In these instances, you’d have to ask: how did the contract get over the line? What should the board and management have asked before approving a new software platform that could introduce risk into the business?
But first, what risks could be introduced to your environment?
Third-party suppliers can create hidden data risks
Your software vendor’s supply chain may have hidden cybersecurity risks. As part of the hospitality sector, you’ll appreciate the importance of supply chain integrity. You know it only takes one weak link to create problems elsewhere.
The Australian Signals Directorate recommends understanding your supply chain, assessing suppliers, controlling access to systems and data, and monitoring third-party services.
You may also have little control or visibility over what happens to your data once another provider can access it.
In one example, a data and analytics provider had extracted club data from internal systems, then stored that information in individual Microsoft 365 environments. The provider then shared the data externally via OneDrive links and email. They not only created multiple copies of sensitive data but also introduced another third party into the data-processing chain.
With every connected platform in your technology environment potentially creating another pathway to your data, it’s critical to understand whether your systems, and the vendors connected to them, are as secure as you think.
API security is really a governance issue
APIs allow different applications to exchange information. That means your membership, marketing, payments and other systems can work together without relying on manual processes.
But an API can also provide a pathway into your systems and data.
So, API security isn’t just a technical consideration. Before connecting another platform, someone in the business needs to understand what it can access, what information it can extract, where that information goes and who else may have access to it.
These questions need to be asked at management and board level. The consequences of not asking can include business disruption, loss of sensitive information, compliance issues, financial impacts and reputational damage. Management is responsible for operational outcomes and protecting revenue, while boards have responsibility for risk and governance. As we’ve discussed before, technology now affects all of these responsibilities.
The API itself may be technical, but deciding whether the risk it creates is acceptable to your business is a governance decision.
Boards and management need to ask questions earlier
In their enthusiasm for improvement, it’s not unusual for organisations to overlook cybersecurity and data risk when selecting new software. The sales conversation naturally focuses on what the platform does, what problems it solves and how much it costs.
They’re important considerations, but security needs to be part of that conversation too.
Planning needs to happen before implementation. Security implications need to be understood. IT advisers need to be involved earlier. Boards and management also need enough information to make an informed decision about risk.
That doesn’t mean your board needs to become a room full of cybersecurity experts. Its role isn’t to decide which technology to buy. It’s to ensure technology investments support the organisation’s objectives, deliver appropriate returns and manage risk.
Five questions to ask before you sign that contract
Before committing to a new software provider, ask:
- What systems and data will the platform be able to access? Understand what information is being shared and whether that level of access is genuinely necessary.
- Where will our data be stored, and how will it be protected? Establish where the data goes, whether it’s encrypted in transit and at rest, and who can access it.
- Does the vendor use other third parties to process or store our data? You need to know who else may handle your information. A cybersecurity weakness elsewhere in the supply chain can introduce risk into your own environment.
- How will the platform integrate with our existing environment? An integration can affect networks, permissions, authentication and other systems, so understand the implications before agreeing to proceed.
- Has our technology or security partner reviewed it? A review before you sign gives you the opportunity to identify risks and raise them with the vendor. Once the contract is signed, your options may be much more limited.
The data waiver process
Being asked to implement potentially risky applications after contracts have been signed has led JEM to introduce a data waiver process.
The process gives our customers two paths: implement the solution immediately while acknowledging the identified risk or conduct a security and integration review before implementation.
We recommend the review every time.
By the end of the review process, our customers have a clearer understanding of how the solution integrates with their existing systems, the network implications, internal versus external access, where data is stored, whether data is encrypted in transit, and the overall implementation risk.
The review isn’t there to add another hurdle. It helps our customers understand what they’re agreeing to before they proceed.
Ask before you sign
Every new platform or integration can create another pathway to sensitive business and member data. That doesn’t mean avoiding new technology. It means understanding what you’re connecting, who will have access and what risks come with it.
Security, governance and vendor due diligence belong at the beginning of the buying process, not the end. So, bring your technology partner into the conversation early, while there’s still time to ask questions, address concerns and make an informed decision.
The best time to uncover a potential problem is while you still have the option to act. A little due diligence now can prevent a much harder conversation later.
Talk to JEM
Considering a new platform or integration? Talk to JEM before you sign. We’ll help you understand the security and integration risks so you can make an informed decision before committing.
