description
| - Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
- Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
- Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
- Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
- Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
- Attibute-based Access Controls that apply to all ODBC, JDBC, ADO.NET, OLE DB connnections
to a target database. Default attributes include username, machine name or network address,
client application operating system, and administrator configurable domain. This functionality
provides data access policies that enable control over read and write modes available to ODBC,
JDBC, ADO.NET, or OLD DB connections as applications and service usage evolves. For example,
transparently enabling read-only mode when an application is being used outside the office thereby
thwarting hacks that might occur over WiFi connections. Or implications of different users operating
the same application from a common device where each has different privileges.
|