As best practices for managing vendor access, we recommend these five steps:
Step #1: Consolidate Third-Party Organizations
Consolidation doesn’t have to happen all at once. You can begin with finance and procurement. Any contractor providing services to any department in your company should be identified and cataloged in an authoritative System of Record (SoR) that includes any standing access privileges assigned to current users. There should be multiple gateways for onboarding, including delegated and federated onboarding.
Your company should scan usage records to determine the last time third-party organizations used the credentials. This step allows you to locate and mitigate orphaned accounts. Credentials that have not been used in a specified time should be flagged for follow-up and de-provisioning if the user has left or is in a different role.
This is also a great time to assign sponsorship and joint accountability to third-party administrators. These administrators have better visibility to joiners, movers, and leavers from within their companies and should be the focal point for recurring access reviews and certifications. Service-level agreements (SLAs) that stipulate the third-party organization’s responsibilities and commitment to administrative support should be included as contract renewals occur.
Step #2: Institute Vetting and Risk-Aware Onboarding Processes
Your company and the vendor need to determine a workflow for vetting and onboarding users to ensure they are who they say they are and that their onboarding process follows the concept of least privilege. They should be given only the appropriate access to complete their assigned roles. The role definitions should be specific to the actual tasks and not simply duplicated because the roles are similar.
Having a clear workflow between your company sponsor and the third-party administrator will reduce the phone calls and emails that typically slow down the process.
Step #3: Define and Refine Policies and Controls
Your company and the vendor should define and continually optimize policies and controls to identify potential violations and reduce false positives, which helps reduce administrative workload.
Test policies and controls regularly – monthly or quarterly – with the administrators from your company and third party. Running periodic access reviews and ongoing certifications will help ensure no user is over-provisioned and that orphaned accounts won’t provide a conduit into sensitive data.
Step #4: Institute Compliance Controls for the Entire Workforce
Vendor access is rising in importance with several regulatory frameworks and is becoming a focal point for auditors. For example, Sarbanes-Oxley (SOX) includes several controls for managing third-party risk:
- APO10.01/APO10.02: Vendors must be selected per the organization’s third-party vendor risk management policy and processes
- APO10.03: A designated individual must regularly monitor and report on whether third parties are meeting the organization’s service level performance criteria
- APO10.04: Third-party service contracts must address the various risks, security controls, and procedures to protect information systems and networks.
Ultimately, the goal is to bring all vendor access under the same compliance required of employees, so there is consistency across the entire workforce, and any violations get mitigated quickly. You can tie compliance controls to user type and enact auto-remediation policies to take swift action on non-compliant identities.
Having out-of-the-box regulatory compliance reports for Sarbanes-Oxley, HIPAA, GDPR, PCI-DSS, and others makes it easier to enforce compliance controls and more efficient to provide audit documentation.
Step #5: Implement Converged Governance
Once you complete the first four steps, you can raise your cybersecurity maturity through converged governance of your entire workforce using a combination of IGA, Privileged Access Governance, and Third-Party Access Governance.
Using a system that provides a converged view gets you a single-pane-of-glass for complete visibility of your entire workforce. It also provides another level of safety by immediately revoking access to downstream systems if warranted and providing time-based access so that access gets revoked when a contract ends. Adding Application Access Governance can allow you to identify potential and actual cross-application Separation of Duty violations across SaaS and on-premises applications.