iSight

iGuard

Architecture

BI Application Integration

________________
Customer Success
Solutions Demonstration

Awards

Collateral

 

                                                    

_____________________________________________________________

iGuard - Usage Policy Management Improves Performance and Compliance

 

 

Manages  and Guides How Application Users Access and Interact With Data - Automatically

 

Applications such as BI, CRM or data warehousing are subject to unpredictable use from growing numbers of people, all seeking quick and accurate access to information. Unknowingly and inevitably, these users issue inappropriate, unauthorized, or "runaway" reports and queries that deliver incorrect results, breach information security policies or degrade performance of the entire system.

 

In response, Teleran offers iGuard, a patented SQL policy manager that improves performance and availability in real-time while protecting sensitive information. iGuard prevents a wide range of user problems commonly associated with application use. It protects the database from unauthorized, inappropriate and wasteful queries, improves overall system performance, enforces compliance policies and increases user productivity. iGuard also includes a unique user messaging facility that guides and informs application users if they violate an active iGuard policy. iGuard messaging improves user productivity and performance while reducing helpdesk calls and support costs.

 

 

The Data Warehousing Institute

"The Data Warehousing Institute sponsors the annual Pioneering Product Award to recognize innovative solutions that will most likely revolutionize the practice of data warehousing. Teleran’s iGuard was the clear winner, having met TDWI’s evaluation criteria of innovation, usefulness, value, impact and uniqueness."

 

Enforces data compliance policies at database object & row level

Prevents problem queries before they waste time & resources

Improves query performance & prevents user errors


 

Enforces Data Compliance Policies at Database Object & Row Level

Driven by compliance and data privacy regulations such as the Sarbanes-Oxley Act (SOX), the Gramm-Leach-Bliley Act (GLBA), and the Health Insurance Portability and Accountability Act (HIPAA), implementing and enforcing effective data security and privacy policies are more important than ever.

 

Database and application level approaches to enforcing data security are often inadequate and administratively costly. Database access controls are resource intensive, degrading application performance and increasing administrative overhead. Increasingly organizations authenticate and authorize users at the application level, and do not pass user IDs to the database. Without a means of identifying individual users, database access controls are rendered useless. On the other hand, building access controls into each and every application becomes prohibitively expensive and difficult to maintain as the number of applications grow across organizations.

 

Delivering a cost effective and centrally managed approach to enforcing data security and privacy policies becomes essential. iGuard Access Policies act as a database "firewall", managing access to specified schemas, tables, columns and rows by user, user group, role or application. iGuard works in conjunction with most single sign-on and application specific authorization and authentication programs and products. It delivers a consistent layer of compliance policy enforcement independent of application and databases.

Merrill Lynch

"As our user community grows, iGuard policies have enabled us to guide and support more people at a reduced cost, maximizing the business value of our applications."

Prevents Problem Queries Before They Waste Time & Resources

Acting as a "filter", iGuard screens each query as it travels on the TCP-IP network between any SQL-generating application and the backend databases. Unlike database governors, iGuard’s pre-emptive user governance facility functions outside of the database, examining and preventing user queries before they reach the database and impact valuable system resources and waste users' time and productivity.

 

iGuard Policies can prevent different kinds of user problems including inappropriate, unauthorized or inaccurate reports and queries. Information requests that violate an active iGuard Policy are either prevented or flagged for later analysis and an iGuard user message is automatically sent to user guiding them to improve the efficiency or effectiveness of their queries.

Intelligent Enterprise

"Teleran’s system is an unmatched tool for dynamic query management. It provides analysis information, structural recommendations, and proactive query controls previously only dreamt of."

Improves Query Performance & Prevents User Errors

Inevitably user errors occur as new data is added, or new users come on-line and are unfamiliar with the applications or the database. With iGuard Customizable Policies selected from the Policy Library you can prevent performance degrading query errors. And, using the iGuard "point and shoot" Policy Wizard, you can tailor policies to address query and reporting issues unique to your users, applications and databases. Here are several examples:

  • Do not do a SELECT from the claims table without a REGION code (Example: Regional claims analysts should never query claims history for the entire country)

  • Do not permit a join between TABLE A and B without column A (Queries issued without an indexed column are too resource intensive)

  • During the day shift, do not permit unqualified access to TABLE A and TABLE B, but permit such access during the evening and night. (Maintain peak period performance by deferring long-running queries to later shifts)

  • Do not join a fact table to itself (Prevents Cartesian join or "runaway" queries)

  • Do not allow a SELECT * from a fact table without a WHERE clause (Prevents unconstrained queries from consuming significant system resources)

Customizable Policies can also prevent user errors that generate inaccurate or misleading results. Here are some examples: 

  • Do not join two fact tables to each other without qualifiers (Prevents incorrect results)

  • Do not join TABLES A and B (Prevents a "Chasm Trap", a many-to- one-to-many join that results in incorrect answers)

Back to top

 

 


 
 

© 2009 Teleran Technologies, Inc.  All rights reserved.  Legal Notices  I  Privacy Policy
973.439.1820  I  info@teleran.com