| |
|
|
BoKS Access Control for Applications — How It Works
BoKS Access Control for Applications is typically used by organizations to provide a higher degree of control for mission-critical applications. While not all applications within an organization will normally be seen as mission-critical, applications that process sensitive business data, or data that is subject to regulatory scrutiny, will often be categorized as "high risk" applications.
These can include applications processing financial data that may be subject to accounting legislation, and applications that contain customer data that must be kept confidential. BoKS Access Control for Applications provides safeguards to data integrity since it helps ensure that only authorized users are accessing data via these applications. The solution also provides a centralized log of all applications accesses, making the IT auditing process much easier.
In partnership with application vendors, BoKS Access Control for Applications delivers a powerful set of features that help organizations standardize their application access controls across the enterprise. The increased confidence in controlling access to vital applications and data also improves an organization's ability to share applications across the extended enterprise.
Available for:
- Older SAP Solutions utilizing ABAP client server technology, including R/3T
- SAP Solutions utilizing Java and ABAP based on NetWeaverT technology
- Oracle Client/Server Applications
- Oracle Portal Applications
For customer-specific applications, we provide a programmable library that allows you to provide the same security management, SSO, and central services logging.
Here's an example: An employee is securely logged into your network. She has inherited a User Group, and a set of security policies from the BoKS infrastructure. When attempting to connect to an enterprise application, the Access Control for Applications agent will.
- Make a policy check if the user is allowed to attempt to connect to this service
- If approved, download any connection information needed
- Make a secure connection to the chosen application server(s)
- Based on policies set in the BoKS infrastructure, optionally ensure the session is encrypted end to end
- Connect to the FoxT Agent installed with your enterprise application
- Which checks the user is allowed onto this service
- And if approved, connects directly into the application using a Single Sign On (SS0) API
- The user does not see any of the security dialog, nor a username/password page
- Central logging of access requests are stored in the BoKS infrastructure for review and reporting
|
|
|
