geolocation-mobile.jpg

Data Location Awareness

 

Technical Details -

  • DataLenz runs on IBM Z mainframes with supported releases of z/OS. 

  • Installation of the DataLenz z/OS agent is simple and straight-forward, along with limited network configuration.

  • DataLenz supports all z/OS data types.

  • Data access start and end events are recorded for specified datasets, and kept in mainframe-based logs, accessible for reporting and real-time monitoring and alerting through the graphical interface.

  • The administrative and reporting interface runs as a workstation client, with secure access to your IBM Z mainframes running the DataLenz agent.

The patent pending DataLenz technology tracks the location of your employees, partners, contractors, and rogue actors, with the actual IP address of the device they are using, even if they are going through VPN or using NAT.

Who might use Geolocation?

Of course, Geolocation software has not been in common use on the IBM Z mainframe because, until now, it hasn’t been available. But there’s another reason: the personnel who have traditionally been responsible for securing the mainframe have often been focused on IDs and resource accesses, and allowed network management and security personnel handle outside sources of access.

who-uses-geolocation.png

In addition to that, however, Geolocation is intrinsically a legal and strategic business need, the customers of which are members of the “C Suite” and key organizational units such a legal, auditing, accounting, and owners of the applications whose data have geographical sensitivity. It is when they become aware of the needs and the solution that traditional IT are then informed by them of this irrefutable mandate.

Likewise, if you are outsourcing your data to a provider with whom you have an SLA, that agreement likely doesn’t specific granular access control to sensitive data and applications based on dynamically-changeable geographic criteria, so it is the nature of your organization that will dictate this requirement, and the need to have a solution installed, configured, and managed to respond to it.

What types of organizations need Geolocation?

And what does your organization do that mandates such preemptive protection? Here is a list of some of the types of organization that need Geolocation for their IBM Z mainframe data and applications:

  • Federal, state/province, city, and other local governments for citizen data and other sensitive information that need to remain local-access-only.

  • Publicly-funded organizations such as military and intelligence, where extremely sensitive data may need to be accessed by high-level personnel in doing their jobs overseas, but some must also be prevented except from the most trusted enclaves.

  • Banking and credit card organizations, where accessing certain types of fund or customer information offshore can violate laws, regulations, and embargos.

  • Manufacturing organizations that not only have sensitive customer data, but also partner/supplier information that could be misused competitively by rogue governments and the businesses aligned with them.

  • Insurance and other financial industry organizations, whose data may be subject to a wide range of legal limitations about extraterritorial access.

Would you like to know more about DataLenz? Send us a message.