S4X for Planning & Executing Mass Security Changes

Planning Mass Security Changes

With Security 4X administrators can have the confidence that they plan, model, and test mass security changes before implementing a large-scale change. With Security 4X administrators can carry out the following types of tasks which are virtually impossible without a purpose-built tool. They can: establish a baseline of current security settings in a centralized database; completely wipe away, rebuild, and migrate security from one geography, platform, and/or tier to another; have full logging and reporting regarding mass changes; and, maintain corporate audit standards simultaneously.

With Security 4X, any of the following types of mass changes are possible:

      1. Tier to Tier – moving security between dev, test, and prod
      2. Geographic/Departmental – pushing security to various geographic/departmental servers
      3. Cross Platform – transferring security from Apache Directory to Google Groups to HCL Domino to IBM Cognos to Microsoft Active Directory to NetIQ eDirectory to Okta to IBM Cognos – or any variation of these

Administrators need the ability to make security changes on a user-by-user basis, but also need the ability to make large scale, mass changes.

Updated image S4X for mass security changes - managing environments
Security 4X offers a host of features for managing environments on a broad scale, including:


Moving security from one Environment to another Environment

Moving security from one environment to another or to various geographic/departmental servers en masse is all part of Security 4X's design. Security 4X is designed to address mass changes that can only be reliably implemented through automation. This includes wiping an environment totally clean, redesigning the group/membership structure in a worksheet, importing the security changes into the Security 4X actions log, and mass implementing an entirely new structure.

Moving security from one Platform to another Platform

Security 4X is designed in such a way that you can design security at the database level and implement it in your target platform when ready. It starts with a security export from your current platform, continues with developing the new security design in Security 4X, and then implementing it in your new platform. If you are moving from one security platform to another, Security 4X provides automation and reporting before, during, and after the migration. Security 4X supports these platforms: Apache Directory, Google Groups, HCL Domino, IBM Cognos, Microsoft Active Directory, NetIQ eDirectory, and Okta.


Security Automation

Security 4X provides security automation for all security transactions that are important to implementing enterprise security en masse. No more manual changes. All changes are implemented through governed processes.

Reversing a Series of Security Changes

Changes may be reversed via easy-to-implement scripting that can be mapped in Excel and then run through the Security 4X processing engine.

Testing and Auditing

Security Snapshots

Security 4X provides tools that allow you to snapshot your entire environment so that you have an up to the minute baseline of security status.

Log of every Security Change

Security 4X logs every change made to an environment. Every security change is logged by time, administrator, the type of security change being made, and precisely what was changed.

Security Reporting

Security 4X provides 25+ standard security reports so that you have visibility into current state and historical changes.

What Our Customers Have to Say