Cloud computing

Available (332)

Showing 1 - 12 per page



20151 Information technology — Cloud computing and distributed platforms — Dataspace concepts and characteristics

Body

20151 Information technology — Cloud computing and distributed platforms — Dataspace concepts and characteristics

As a StandICT fellow call 6, I would like to call your attention to the current working draft of 20151 on Dataspace concepts and characteristics, produced by ISO/IEC JTC 1/SC 38/WG 6 Data, interoperability and portability. As convenor of this group I want to ensure this work when completed is widely adopted.

The working draft is available to experts of the national standardization bodies through the OSD. On March 17th 2025 the ISO/IEC JTC 1/SC 38 plenary will be held with further working group meetings. This is an opportunity to join the discussion and learn more about this standard.

Please join our working group and review this document as we go through the comments disposition processes. 

Dataspaces provide a scalable and more automated approach to organizational agreements, and supporting software services that together enable trusted data sharing. This standard provides a discussion on high level concepts in Dataspaces. We anticipate that it be the entry point for other standards in the area. National bodies have the opportunity to join our working group and discuss the document further.

Please join ISO/IEC JTC 1/SC 38/WG 6 Data, interoperability and portability to get involved in this standard and other standards in Data, interoperability and portability.

As a StandICT fellow of call 6, I will work with you on the adoption of 20151. 

 

Tags

Observability and ISO/IEC 22123-2:2023

Body

Standards discussed:

  • ISO/IEC 22123-2:2023 Information technology — Cloud computing Part 2: Concepts

ISO/IEC 22123 part 2 describes the concepts relevant to cloud computing. Parts 1 and 3 cover vocabulary and the reference architecture respectively. Whilst many of the standards do not call out observability explicitly they do include reference to the concepts. This discussion is provided to briefly show how observability plays a crucial role in ensuring that cloud services are performing as expected and meeting the needs of both the Cloud Service Consumer (CSC) and the Cloud Service Provider (CSP). Observability encompasses the monitoring, analyzing, and interpreting of system behaviors and performance indicators, which are critical for maintaining service quality, security, and operational efficiency. 

1. Monitor Service Quality

The activity of monitoring the service involves tracking the performance and quality of the cloud services provided by the CSP to the CSC. This activity ensures that the service is meeting the agreed-upon levels in the Service Level Agreement (SLA) between the CSC and CSP. Observability is integral to this process, as the process requires:

  • Tracking usage: Monitoring how much the service is being used, and by which users, ensures that resource consumption aligns with expectations and avoids misuse.
  • Service Integration Monitoring: Observing how well the cloud services integrate with the CSC’s existing ICT systems helps ensure business objectives are being met, identifying any disconnects between the cloud service and on-premise systems.
  • Defining and measuring performance indicators: Key indicators such as service availability, outage frequency, mean time to repair, and provider responsiveness are established, and observability tools ensure these metrics are continuously measured and analyzed.
  • Archiving indicator data: Storing performance data for historical analysis is crucial for future troubleshooting and auditing.
  • Service comparison: Comparing actual service performance with the agreed-upon service levels allows for the identification of gaps or issues in service delivery.

2. Service Trial and Testing

Before full-scale deployment, CSC can engage in a service trial to test the suitability of the CSP’s services for their business needs. During this phase, observability can help monitor how well the cloud service performs in real-world scenarios. Key activities include:

  • Provisioning and authentication: Ensuring secure access through user credentials and authenticating the CSC before they begin using the trial service.
  • Testing the service: Observability during the trial ensures the service meets performance and business requirements, providing valuable data to assess if the service is fit for use.

3. Administering Service Security

Observability is essential for the CSC to ensure that their data is protected within the cloud. This includes monitoring security policies, ensuring compliance with backup and recovery plans, and defining encryption methods. Observability tools can:

  • Monitor encryption technologies applied to data at rest and in motion to prevent unauthorized access or tampering.
  • Track the execution of backup and failover plans to ensure data integrity and availability, particularly in disaster recovery scenarios.

4. Handling Problem Reports

If issues arise during the use of cloud services, observability plays a significant role in the CSC’s ability to handle problem reports. The process includes:

  • Impact assessment and troubleshooting: Observability tools help assess the scale and impact of the problem, identifying the root cause and enabling quick troubleshooting.
  • Tracking problems with the CSP: Problem resolution is tracked, with observability tools ensuring that each issue is addressed within the agreed-upon timescales, and escalated if necessary.

5. Provide Billing and Usage Reports

Observability is not only about monitoring service performance but also about tracking the usage and billing aspects of cloud services. By integrating observability into the cloud system, CSC can:

  • Continuously monitor resource consumption and service usage, which informs billing and invoicing processes. This ensures that usage data is accurately reflected in the reports provided to the CSC business manager.
  • Ensure that the billing aligns with actual service consumption, avoiding overbilling or underbilling, and providing transparency into how cloud resources are utilized.

Conclusion

In cloud computing, observability is essential for maintaining a seamless, secure, and efficient relationship between the CSC and CSP. By providing detailed insights into service performance, security, and usage, observability ensures that cloud services meet business requirements, remain secure, and deliver the expected outcomes. Whether it's monitoring service quality, administering security, handling problems, or managing billing, observability helps ensure that cloud computing environments are reliable and perform optimally for all stakeholders involved. ISO/IEC 22123 part 2 describes these cloud computing concepts but the application of observability can provide a strong contribution to the enhancement of quality. 

Data aware networking (information centric networking) – Requirements and capabilities

This Recommendation specifies the requirements and capabilities of data aware networking (DAN) to realize the use cases and scenarios described in ITU-T Supplement 35 to Recommendation Y.3033, Data aware networking - Scenarios and use cases, which are expected to be major applications/services provided on DAN. One of the objectives reflecting emerging requirements for future networks (FNs) is data awareness as specified in ITU-T Recommendation Y.3001 - Future networks: Objectives and design goals. DAN is expected to have capabilities optimized to handle enormous amount of data and to enable users to access desired data safely, easily, quickly, and accurately, regardless of their location by making information the destination of request delivery. DAN can be rephrased as the networking whose central concern is retrieving information, i.e., information centric networking (ICN).

Security requirements of Network as a Service (NaaS) in cloud computing

Network as a Service (NaaS) is one of the representative cloud service categories, in which the capability provided to the cloud service customer (CSC) is transport connectivity and related network capabilities. NaaS services can provide any of three cloud capabilities as: NaaS application service, NaaS platform service and NaaS connectivity service. All the three kinds of NaaS service face particular security challenges such as application security vulnerabilities, security risks of network virtualization, eavesdropping, etc. Recommendation ITU-T X.SRNaaS analyses the security challenges and security requirements of NaaS application, NaaS platform and NaaS connectivity. This Recommendation could help NaaS service providers to address on the security issues. The capabilities provided by this Recommendation will take into account the national legal and regulatory obligations in individual Member States in which the NaaS services operate.The methodology of this proposal would follow the recommendations of clause 10 in Recommendation ITU-T X.1601.

Security requirements of public infrastructure as a service (IaaS) in cloud computing

Infrastructure as a Service (IaaS) is one of the representative categories of cloud services, in which the cloud capabilities service provided to the CSC is an infrastructure capabilities type. IaaS environments and virtualized services are facing more challenges and threats than traditional information technology infrastructure and application. Platforms that share computing, storage, and network services need protections specific to the threats in the IaaS environment. If these threats are not carefully addressed, it will have very negative impact on the development of IaaS services.Recommendation ITU- X.SRIaaS aims to document the security requirements of public IaaS. This will be helpful for IaaS CSPs to improve the overall security level throughout the planning, constructing and operating stages of IaaS platform and services. This work also complements the security standardization activity related to Software Defined Networks

Security requirements for Communication as a Service application environments

Recommendation ITUT X.SRCaaS recommends the security requirements of communication as a service (CaaS) application environments with the identification of the risks. The Recommendation describes the scenarios and the features of CaaS, into which multicommunication capabilities are plugged. Moreover, some special /unique risks are identified, which are caused by the unique features of CaaS. The corresponding security requirements are recommended for the following aspects: Identity fraud, orchestration security, multi devices security, countering spam, privacy protection, infrastructure attack, attack from infrastructure, Intranet attack and so on. The Recommendation refers to the common security requirements of Recommendation ITUT X.1602 to avoid duplicated work. These measures in the requirements take into account the national legal and regulatory obligations in individual member states in which the platforms operate. The work applies the methodology standardized in clause 10 of Recommendation ITU-T X.1601.

Security requirements for software as a service application environments

Recommendation ITU-T X.1602 analyses the maturity levels of software as a service (SaaS) application and proposes security requirements to provide a consistent and secure service execution environment for SaaS applications. These proposed requirements originate from cloud service providers (CSP) and cloud service partners (CSN) as they need a SaaS application environment to meet their demands on security. The requirements are general and independent of any service or scenario specific model (e.g. web services, or representational state transfer (REST)), assumptions or solutions.

IEEE Standard for Adoption of OpenFog Reference Architecture for Fog Computing

OpenFog Consortium--OpenFog Reference Architecture for Fog Computing is adopted by this standard. OpenFog Reference Architecture [OPFRA001.020817] is a structural and functional prescription of an open, interoperable, horizontal system architecture for distributing computing, storage, control and networking functions closer to the users along a cloud-to-thing continuum of communicating, computing, sensing and actuating entities. It encompasses various approaches to disperse Information Technology (IT), Communication Technology (CT) and Operational Technology (OT) Services through information messaging infrastructure as well as legacy and emerging multi-access networking technologies

CWL, Common Workflow Language Standards, v1.2

The Common Workflow Language (CWL) is an open standard for describing analysis workflows and tools in a way that makes them portable and scalable across a variety of software and hardware environments, from workstations to cluster, cloud, and high-performance computing (HPC) environments. CWL is designed to meet the needs of data-intensive science, such as Bioinformatics, Medical Imaging, Astronomy, High Energy Physics, and Machine Learning.

CWL is developed by a multi-vendor working group consisting of organizations and individuals aiming to enable scientists to share data analysis workflows. The CWL project is maintained on Github and we follow the Open-Stand.org principles for collaborative open standards development. Legally CWL is a member project of Software Freedom Conservancy and is formally managed by the elected CWL leadership team, however, every day project decisions are made by the CWL community which is open for participation by anyone.