Zero Trust is gaining widespread acceptance, and organizations face various hurdles in its implementation. How are you implementing Zero trust in your organizations?
3.7k views1 Comment
Sort by:
Content you might like
Company financial stability59%
Industry trends49%
Length of time in business37%
Recent layoffs or restructuring55%
Employee turnover rate51%
Compensation28%
Culture49%
Blindly following Review sites (eg. GlassDoor)4%
Other(s)2%
How long does your organization retain original systems logs used to filter SOX-related actions into a system that requires review of the logs and retains the filtered logs for seven years? Does your organization consider those original system logs records subject to record retention requirements, or supporting information used to create the SOX records?
90 Days14%
365 Days37%
3 years33%
5 years8%
7 years8%
Other (share in the comments)
Below are a few strategies that organizations should keep
in mind while crafting the plan to implement Zero Trust for
their SaaS environment.
A. SaaS Vendor Assessment
Before procuring a SaaS product, thoroughly review the
SaaS vendor’s security policies, data backup and recovery
policies and their approach toward securing the platform
against vulnerabilities. Organizations should have an
inventory of approved SaaS tools that have been vetted by
the security teams and prevent employees from installing
and using unapproved SaaS tools that can expose the
organization to compliance and security risks.
B. Employee Training
Before teams start implementing SaaS applications, employees need to be familiar with the SaaS tool, security best
practices the tool offers and how zero trust principles can
be applied.
C. Identity Management
Implement Single Sign On (SSO) in combination with
multifactor authentication (MFA) for users to use a single
password to login to the network but confirm the user’s
identity every time they login to the SaaS application,
thereby adding an additional layer of security.
D. Obervability, Logging and Monitoring
Real-time monitoring and logging of user and API activities,
such as user logins and sessions, API response times, is
crucial for tracking unexpected behavior of users or critical
application components. This ensures swift action against
any suspicious activities.