<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>UCSC Digital Library Collection:</title>
    <link>https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2688</link>
    <description />
    <pubDate>Tue, 28 Apr 2026 11:52:19 GMT</pubDate>
    <dc:date>2026-04-28T11:52:19Z</dc:date>
    <item>
      <title>Policy based Electronic Medical Record System</title>
      <link>https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2693</link>
      <description>Title: Policy based Electronic Medical Record System
Authors: Ranaweera, D.P.L.K.
Abstract: Even before current social network and cloud computing booms, people identified their medical&#xD;
record information as a key private data source has to be protected with proper systems and&#xD;
procedures. At present, vast publicity received on adverse affects on privacy critical data in&#xD;
both social networks and cloud computing, and that always raise concerns on medical record&#xD;
systems too; most of the time medical record systems have more privacy critical information&#xD;
than aforementioned environments. A main reason for incapability of protecting privacy other&#xD;
and general security requirements in applications are as they do not have proper security mechanisms&#xD;
in place which are suited for their application needs.&#xD;
OpenMRS is a well-known medical record system and our work describes a better way of&#xD;
handling access control in it. We describe a case study to evaluate whether better access control&#xD;
can be placed on OpenMRS using XACML. In addition to that, one of the goals of this work is&#xD;
to preserve existing fine-grained access control in the OpenMRS and extend it for the different&#xD;
needs. Prior to this work, OpenMRS is using a Role Based Access Control (RBAC) model to&#xD;
restrict user actions. RBAC gives administrative nightmare in large/dynamic systems with role&#xD;
explosion. Also existing access control mechanism add constraints on extension for different&#xD;
needs.&#xD;
In our implementation, we integrate standard XACML based components in to OpenMRS. Then&#xD;
evaluate our solution with several types of security polices, whether those policy types can&#xD;
be used with new implementation or not. Finally a generalization of our proposed solution&#xD;
presented to reuse it in other domains of enterprise applications.</description>
      <pubDate>Mon, 23 Jun 2014 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2693</guid>
      <dc:date>2014-06-23T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Security Model for NFC Enabled Smart Phone Based Identity Cards</title>
      <link>https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2692</link>
      <description>Title: Security Model for NFC Enabled Smart Phone Based Identity Cards
Authors: Almeida, P.R.D.N.N.A.De.
Abstract: Usage of smart phones is rapidly increasing. Near Field Communication (NFC) is a new feature incorporated in smart phones. Introducing an Identity card in a NFC enabled smart phone is a new instance of a NFC based application. This research comprises of a security model for such an application. A concept of binding the information of an identity card, to the user and to the phone is presented. A generic architecture is proposed and a prototype is developed as a feasibility study. Two uses cases are elaborated if the NFC enabled smart phone is used as a National Identity Card.</description>
      <pubDate>Mon, 23 Jun 2014 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2692</guid>
      <dc:date>2014-06-23T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Secure Electronic Mobile Cheque Book</title>
      <link>https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2691</link>
      <description>Title: Secure Electronic Mobile Cheque Book
Authors: Dasanayaka, H.D.G.
Abstract: Cheque transaction is one of the highly used money transfer methods in financial&#xD;
world. Even though online money transfer methods are also used in&#xD;
these days, cheque transactions are still popular among many people. But,&#xD;
the existing manual process associates with many issues such as high cost,&#xD;
time consuming, having large impact on environment due to high paper consumption&#xD;
and cheque frauds. In this thesis an attempt is made to explore&#xD;
a way to use the latest mobile technologies to execute day to day cheque&#xD;
transaction securely and efficiently by addressing above issues. Base concept&#xD;
of the proposed M-Cheque system is, facilitating to use digital cheque paper&#xD;
on smart phone of the customer and allow him to transfer it securely&#xD;
to the recipient. Near Field Communication (NFC) technology is used for&#xD;
the communication between issuer’s and receiver’s smart phones. After receiver&#xD;
deposits the cheque, issuer bank, receiver bank and clearing system&#xD;
communicate with each other to process the cheque and finally settle both&#xD;
parties’ accounts by providing a faster service. Security is a main concern&#xD;
for this application and data transferred through this system is secured using&#xD;
cryptographic concepts such as asymmetric key algorithm, symmetric key algorithm&#xD;
and digital signatures. Also, client server communication is secured&#xD;
using Secure Sockets Layer protocol. System was evaluated by comparing&#xD;
it with the current cheque processing system under four categories such as&#xD;
cost, time, environmental impact and security. It was concluded that the&#xD;
system has achieved its goals which are low cost, less time consuming, environmental&#xD;
friendly and higher level of security. Still only less number of&#xD;
people uses smart phones and only few types of smart phones are equipped&#xD;
with NFC are the main limitations of the proposed system. Despite those&#xD;
limitations, there is a wide space for M-Cheque to become successful due to&#xD;
the promising future of NFC in mobile payments, gradually increasing use&#xD;
of smart phones and lots of new mobile device vendors are applying NFC in&#xD;
their new mobile products.</description>
      <pubDate>Mon, 23 Jun 2014 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2691</guid>
      <dc:date>2014-06-23T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Video Steganography</title>
      <link>https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2690</link>
      <description>Title: Video Steganography
Authors: Munasinghe, N.A.W.
Abstract: Hiding messages for various security purposes had become high interesting topic on&#xD;
now days. Encryption provides the ability of data hiding. With the development of the&#xD;
technology, people tend to  gure out a method which is not only capable in hiding a&#xD;
message, but also capable in hiding the existence of the message. Steganography was&#xD;
introduces as a result of those research.&#xD;
The current study is conducted in order to hide a video in a visual  le. The researcher&#xD;
suggests changing the LSB (Least signi cant Bit) of the each byte of the carrier  le. As&#xD;
this method do not add any new data but only change the LSB, this method do not&#xD;
increase the size of the carrier  le unusually. Thus, the existence of the message cannot&#xD;
be detected.&#xD;
There are 2 approaches used in the current study. One is to use the OpenCV library&#xD;
and other approach is to use the avi ll32.dll library. The 1st approach contains some&#xD;
issues as after modifying the frames, the functions of OpenCV create some data padding.&#xD;
This causes to result some garbage data.&#xD;
The 2nd approach was tested and performed well. The system was evaluated by check-&#xD;
ing the ability of hiding the existence of the message and the ability of retrieving the&#xD;
message correctly. Results show that the system had addressed to its research objectives&#xD;
perfectly. The limitations for this research is, the library avi ll32.dll can only used for&#xD;
uncompressed avi  les. In future, when there will be codec introduced for many video&#xD;
types, this method can be implement for all video types.</description>
      <pubDate>Mon, 23 Jun 2014 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">https://dl.ucsc.cmb.ac.lk/jspui/handle/123456789/2690</guid>
      <dc:date>2014-06-23T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

