Securing a Near Cloud Learning Platform

Completed master’s research on securing an Edu-Cloud learning platform through data integrity, access control, and delay-tolerant networking with Near Cloud technology.

The research question

How can an educational platform support learners with limited connectivity while protecting the information and content it distributes?

My completed master’s research, Design and Demonstration of Secure Edu-Cloud Learning Platform from Delay Tolerant Networks, addressed this question through Near Cloud technology. The work brings together resilient communications, information integrity, and application security.

Thesis adviser: Dr. Nathaniel Libatique

The work was motivated by the disruption to education during the COVID-19 pandemic and the difficulty of relying on continuously available internet access. The platform architecture connects learners’ smart devices with Edu-Cloud, while Near Cloud handles communication and content distribution through delay-tolerant networking.

My research focus

My research placed security at the center of the learning platform’s design, addressing three concrete questions:

  • Record integrity: how should the platform respond when student information or grade records have been altered?
  • Content integrity: can it identify malicious modifications that could harm the platform or a learner’s device?
  • Authorization: can it identify and reject actions a user is not permitted to perform?

These questions connect network design with application security: making content accessible also requires deciding which changes and actions the platform should trust.

Security architecture

The research organized the security design around three platform modules:

  1. Change detection and review. Identify alterations so a teacher or administrator can track a change and accept or reject it.
  2. Access levels. Establish permissions to manage unauthorized access and distinguish what users may do.
  3. Source-code protection. Use access levels to help prevent and detect alterations to the platform’s code.

Research methodology

The methodology examined hashing for message integrity alongside other cryptographic schemes, password generation and management, and user profiles with different modes of access. It organized security approaches into four levels: a baseline without security, adoption of existing solutions, modification of existing solutions, and custom security development.

This structure connects each security objective to an engineering decision: how to recognize a change, who can authorize it, and how much existing security functionality to adapt or build.

Information flow and trust boundaries

The architecture can be understood through the responsibilities of its participants:

Participant or component Responsibility
Learner’s smart device Interact with the learning platform and access educational content.
Near Cloud communication layer Support communication and content distribution under constrained connectivity.
Edu-Cloud platform Manage educational information and user access.
Teacher or administrator Review detected changes and decide whether they should be accepted or rejected.

The security questions arise where information changes hands. Content arriving through the communication layer must be considered separately from a user’s permission to change a record. A delivery mechanism provides access to information; the application’s integrity and authorization controls determine how that information may be trusted and used.

Technical perspective: integrity and authorization

Integrity checking and authorization address different questions. An integrity check asks whether content has changed relative to a trusted reference. Authorization asks whether a particular user is permitted to perform an action on that content.

A hash alone does not establish who created a message: an attacker able to replace both the content and an unprotected reference hash can make them agree. Authenticated integrity mechanisms connect verification to trusted key material. As general technical context, the IETF’s Bundle Protocol Security specification defines integrity and confidentiality services for delay-tolerant bundles. This reference explains the broader security model; it is not a claim that the thesis used that specification.

For an educational platform, these distinctions matter when handling a changed grade record, an updated learning resource, or a request to modify platform code. Detecting a difference is one part of the problem; deciding whether that difference is authorized is another.

Research context

The literature discussion considers trust in delay-tolerant networks, attribute-based access control, distributed attribute issuance, and cryptographic approaches to message protection. It also reviews network threats such as selfish forwarding behavior, black-hole attacks, and flooding.

Research contribution

The completed research connected the educational use of an existing Near Cloud communication technology with a security design centered on record integrity, content integrity, and controlled access. It treated protection of information as part of the learning platform’s architecture, alongside the problem of delivering content when connectivity is limited.

My research contribution focused on the security questions, module design, and methodology for protecting that environment. The work joins network design and analysis with application-level decisions about identity, permissions, and changes to information.

Why this work matters to me

This research connects my interest in network design and analysis with application security. It brings together two engineering concerns: keeping educational information accessible when connectivity is constrained, and controlling how that information can be changed or used.

It complements my sound-source mapping research, which explores another connection between physical systems, software, and interpretation of data.