COBIT governance refers to control objectives for the information and related
technologies (Monica et al.), it has five principles, which the first principle is tailored towards
meeting the stakeholders needs; this involves all the processes, which are tailored towards
identifying the main stakeholders in the implementations and identifying the important steps
towards the same. The min objecti9ve here is value creation through optimizations of resources,
optimization of risks and the optimization of any other material, which is involved in the process.
The stakeholders at this stage may involve the suppliers, business partners, customers and the
consultants, which are external from the enterprise and internal stakeholders such as
management, board, staff and risk managers (Benn et al.).
The second principle involves identifying the enterprise information fully from end to end, it
involves covering all the activities, functions and processes where the information is processed in
the enterprise (Chatterjee et al.). The first steps here involve balancing everything that is
involved to fit the organization needs this is referred to as a business scorecard; this includes the
financial resources to fit the organization without straining.
The third principle involved is cascading the enterprise goals to fit the IT-related goals. the
enterprise goals here like IT compliance and support for business compliance with the laws this
is cascaded to fit with the external laws governing the IT sector such as the government laws and
regulations which states that the all the IT implementations and devices should comply with their
acts and regulations. This objective ensures that the internal rules of the enterprise do not
mismatch with the external ones, which include that of the government or societies.
Besides, COBIT ensures steady holistic decisions running any business. Business decisions
generate an effect that affects a business positively or negatively, thus it is of value to keep and
reuse all past decision that runs a business. COBIT as a cloud hosting company takes hid in
making a decision based on records to improve the present. Some decisions create a negative
impact that ought to be monitored to reduce the recurrence., thus big data is a solution to increase
the chances of achieving the objectives, a strong decision has to be made based on the history.
Hence, CUBOT encourages awareness of records. Like it in the case of big data, COBIT has
encouraged the use of customer data to predict the future of companies and organizations that
use its technology.
In conclusion, the present world has embraced the use of technology in solving business issues.
Some of the most embraced technology revolves around big data, social media, and consumption
in different application systems. The incorporation of this technology has increased the success
rate, in companies, business organizations and Sacco is at large. At the same time, some
challenges affect the management and its governance in terms of security in managing
professional implementation and enterprise environments. Thus, COBIT has improved the
management of the cloud system now and has found a solution for many of the businesses of any
COBIT governance approach in cloud technology. 3
“Achieve Your Career Goals with the Fit That’s Right for You.” IEEE Pervasive Computing,
vol. 16, no. 2, Apr. 2017, pp. 1–1, 10.1109/mprv.2017.41. Accessed 10 Feb. 2020.
Benn, S., et al. “Defining and Identifying Stakeholders: Views from Management and
Stakeholders.” South African Journal of Business Management, vol. 47, no. 2, 30 June
2016, pp. 1–11, 10.4102/sajbm.v47i2.55.
Chatterjee, Sheshadri, et al. “Securing IoT Devices in Smart Cities of India: From Ethical and
Enterprise Information System Management Perspective.” Enterprise Information
Systems, 13 Aug. 2019, pp. 1–31, 10.1080/17517575.2019.1654617. Accessed 20 Oct.
Monica, Cindy, et al. “AUDIT AWAL SISTEM INFORMASI PADA PT. X BERDASARKAN
STANDAR CONTROL OBJECTIVES FOR INFORMATION AND RELATED
TECHNOLOGY (COBIT 4.1).” Jurnal Informatika, vol. 13, no. 2, 1 Feb. 2016,
10.9744/informatika.13.2.33-38. Accessed 17 Feb. 2020.