Products Overview

The Cloud Services Challenge

Today”s strategy is to move services into the cloud. These cloud services have evolved over the last few years and with modern browser technology widely adapted, these cloud services compete with standard in house enterprise level products.

One major difference between these two models, could solutions or on premise solutions are the aspects license costs and security.

License Costs

Most license models for on premise solutions do involve a once off payment with a yearly maintenance fee. In contrast, almost all cloud services are charged on a monthly basis. While the up front investment may be smaller for cloud services, the mid to long term costs can be significant. To keep these costs under control, a tight management of the accounts should be in place, ideally before the new services are rolled out.

It is clearly not enough to rely on the Administrative tools of the cloud vendors and manually create the necessary accounts, or just extend your SSO solution to trigger a new account creation whenever a user logs into the new system. With this approach sooner or later the number of unused accounts will accumulate and so will your monthly subscription base.


Similar to the license aspects of services, there are some distinct differences between on premise applications and cloud services. The on premise application is primarily only accessible from the intranet. If anyone wants to access these applications from the outside, a VPN connection has to be established and all traffic is routed through firewalls. This architecture makes it hard for your employees to collaborate with your customers. Cloud services on the contrast are much easier to access. No VPN tunnel has to be established to access the application which makes collaboration much more efficient. Obviously these cloud services remove at least one barrier for anyone trying to abuse your valuable company data.

To minimize the risk, a tight security model has to be in place also for the cloud services. Any dormant or orphan accounts in your cloud partition presents a potential entry door for an attack. As a first measure of defense, there should be no orphan or dormant accounts. This leads right to the following questions:

  • which accounts should be in the cloud?
  • when and under which circumstances should an account be removed?

How can Kona Enterprise Manager solve these challenges?

Kona EPM can assist you in minimizing the license costs and reducing the risks for your cloud services.

This is done by managing the complete account lifecycle from within EPM.

Planning the accounts

Provisioning of the accounts and assign ownership

Monitoring of active accounts

Terminating accounts

Once such a life cycle is implemented and managed from a centralized system an efficient account governance can be implemented:

  • monitor the account activity
  • implement account approval workflows
  • audit any account changes
  • report and act on policy violations
  • terminate accounts in a timely matter

Legal notice from Kona Communication

Kona Communication GmbH

Amalien Str. 59
D-86633 Neuburg, Germany
Phone +49 231 9999 419

General Manager:
Wolfgang Bergbauer

Commercial Register District Court : Amtsgericht Ingolstadt
Registration number: HRB 6574

Tax number: Identification number according to §27a of the German Tax Law: DE 241 161 258


1. Content
The author reserves the right not to be responsible for the topicality, correctness, completeness or quality of the information provided. Liability claims regarding damage caused by the use of any information provided, including any kind of information which is incomplete or incorrect,will therefore be rejected.
All offers are not-binding and without obligation. Parts of the pages or the complete publication including all offers and information might be extended, changed or partly or completely deleted by the author without separate announcement.

2. Referrals and links
The author is not responsible for any contents linked or referred to from his pages – unless he has full knowledge of illegal contents and would be able to prevent the visitors of his site fromviewing those pages. If any damage occurs by the use of information presented there, only the author of the respective pages might be liable, not the one who has linked to these pages. Furthermore the author is not liable for any postings or messages published by users of discussion boards, guestbooks or mailinglists provided on his page.

3. Copyright
The author intended not to use any copyrighted material for the publication or, if not possible, to indicate the copyright of the respective object.
The copyright for any material created by the author is reserved. Any duplication or use of objects such as images, diagrams, sounds, video or text in other electronic or printed publications is not permitted without the author`s agreement.

4. Privacy policy
If the opportunity for the input of personal or business data (email addresses, name, addresses) is given, the input of these data takes place voluntarily. The use and payment of all offered services are permitted – if and so far technically possible and reasonable – without specification of any personal data or under specification of anonymized data or an alias. The use of published postal addresses, telephone or fax numbers and email addresses for marketing purposes is prohibited, offenders sending unwanted spam messages will be punished.

Please note: The Privacy policy is currently being revised. For questions please contact

5. Legal validity of this disclaimer
This disclaimer is to be regarded as part of the internet publication which you were referred from. If sections or individual terms of this statement are not legal or correct, the content or validity of the other parts remain uninfluenced by this fact.