<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01355nam a2200121Ia 4500</leader>
  <controlfield tag="008">231221s9999    xx            000 0 und d</controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">English</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Ankita R Shekar.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2="0">
    <subfield code="a">AES algorithm to prevent data manipulation in fitness mobile application</subfield>
    <subfield code="b">Nagasundari, S.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">Jan-May 2019</subfield>
    <subfield code="b">PES University</subfield>
    <subfield code="a">Bengaluru</subfield>
  </datafield>
  <datafield tag="510" ind1=" " ind2=" ">
    <subfield code="a">Nowadays there are many mobile applications which are in market. And some are used as the daily day needs like: Gas bill payment, Electricity bill payment, Mobile recharge, Movie tickets booking, Food delivery, Online shopping and last but not the least Fitness tracking. And people are giving more importance for the health. Hence there are plenty of application. Are these applications secure, because these health care applications will store all the user data in the server. So, if the application is not secured properly then the data which is been saved in the server may be hacked or manipulated. In this project AES algorithm is implementing to save the user details. If the AES algorithm is not used, then the data is manipulated, and the application will allow us to open any malicious website and the data of the user is been changed. And fitness application is implemented with and without the AES algorithm, so that there will be changes in the data with respect to security. A</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">CD</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">237120</subfield>
    <subfield code="d">237120</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="r">2024-01-26 00:00:00</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">CD7247</subfield>
    <subfield code="w">2024-01-26</subfield>
    <subfield code="y">CD</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="0">0</subfield>
    <subfield code="a">ML</subfield>
    <subfield code="b">ML</subfield>
    <subfield code="d">0000-00-00</subfield>
    <subfield code="E">CS/PG</subfield>
    <subfield code="G">RS</subfield>
    <subfield code="F">1</subfield>
    <subfield code="V">0</subfield>
  </datafield>
</record>
