<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Information Security Measures for a Procrastination-Combatting Digital Solution *</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Valentyna</forename><surname>Pleskach</surname></persName>
							<email>pleskach64@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Taras Shevchenko National University of Kyiv</orgName>
								<address>
									<addrLine>Volodymyrs&apos;ka str. 64/13</addrLine>
									<postCode>01601</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Irma</forename><surname>Šileikienė</surname></persName>
							<email>i.sileikiene@eif.viko.lt</email>
							<affiliation key="aff1">
								<orgName type="institution">Vilniaus Gediminas Technical University</orgName>
								<address>
									<addrLine>Saulėtekio al. 11</addrLine>
									<postCode>LT-10223</postCode>
									<settlement>Vilnius</settlement>
									<country key="LT">Lithuania</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Romanas</forename><surname>Tumasonis</surname></persName>
							<email>r.tumasonis@eif.viko.lt</email>
							<affiliation key="aff1">
								<orgName type="institution">Vilniaus Gediminas Technical University</orgName>
								<address>
									<addrLine>Saulėtekio al. 11</addrLine>
									<postCode>LT-10223</postCode>
									<settlement>Vilnius</settlement>
									<country key="LT">Lithuania</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="institution">Vilniaus Kolegija |Higher Education Institution</orgName>
								<address>
									<addrLine>Saltoniškių str. 58</addrLine>
									<postCode>LT-08105</postCode>
									<settlement>Vilnius</settlement>
									<country key="LT">Lithuania</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yevhenii</forename><surname>Topolskov</surname></persName>
							<email>y.topolskov@knu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution">Taras Shevchenko National University of Kyiv</orgName>
								<address>
									<addrLine>Volodymyrs&apos;ka str. 64/13</addrLine>
									<postCode>01601</postCode>
									<settlement>Kyiv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Information Security Measures for a Procrastination-Combatting Digital Solution *</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">4F298092070977D70337847FE7DED5E0</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T20:11+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Information security</term>
					<term>security frameworks</term>
					<term>security requirements</term>
					<term>security measures</term>
					<term>risk management</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This paper explores various security frameworks, threat modeling, and risk management techniques, the assignment provided a thorough theoretical backdrop against which practical security measures can be developed and implemented. Covering critical aspects of security such as authentication, data privacy, session management, and compliance with legal standards like GDPR, the work not only addressed potential vulnerabilities identified through threat modeling but also set a solid framework for implementing these security features practically. This comprehensive approach ensures that the prototype is not only functional but also secure from various cybersecurity threats. Moreover, it showcased how security and functionality can be balanced effectively, paving the way for potential future development and real-world application of the prototype.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>The integration of technology into every day has greatly improved personal and professional productivity. However, this digital expansion has also exposed users to complex cybersecurity challenges <ref type="bibr" target="#b2">[3]</ref>. Applications designed to enhance productivity are particularly vulnerable, as they frequently manage large volumes of sensitive data, making them prime targets for cyber threats. In this context, the role of information security is paramount, safeguarding against data breaches, unauthorized access, and other threats that undermine user privacy and trust. Thus, robust information security measures are fundamental for maintaining the confidentiality, integrity, and availability of data.</p><p>Given the complexity of modern cyber threats, which now include advanced tactics like social engineering, ransomware, and sophisticated malware attacks, digital solutions require robust and comprehensive security protocols, as well as the ability to adapt to the rapidly changing landscape of cyber risks <ref type="bibr" target="#b0">[1]</ref>. Additionally, the international scope of digital application deployment mandates adherence to various data protection laws, such as GDPR and CCPA. This complex environment highlights the need for continuous improvement in security strategies to maintain user trust and ensure the integrity of personal data.</p><p>Therefore, the intersection of information security and application development is a critical area of study and application. This study aims to bridge the gap between application development and robust cybersecurity practices, ensuring that digital solutions are not only effective in addressing human behavioral issues like procrastination but are also secure against both current and potential future cyber threats.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.">The CIA triad</head><p>Information security consists of several key principles, each fulfilling a distinct role in addressing the complex threats and vulnerabilities within digital environments. These principles include confidentiality, integrity, and availability <ref type="bibr" target="#b3">[4]</ref>.</p><p>Confidentiality ensures that sensitive information is accessed only by authorized individuals and is protected from those who are not permitted to access it. In digital solutions, particularly those managing personal productivity, confidentiality can be upheld through the use of encryption, secure user authentication methods, and stringent access controls <ref type="bibr" target="#b6">[7]</ref>. For instance, a digital application designed to combat procrastination may store user data related to personal goals and daily activities, which should be accessible only by the user and not be exposed to unauthorized access.</p><p>Ensuring confidentiality is paramount not only for user trust but also for the application's credibility and long-term viability. Users entrust applications with their data, expecting that their information will be handled with the utmost discretion. Breaches in confidentiality can lead to loss of user trust, legal repercussions, and potential harm to individuals whose data may be exposed. Achieving confidentiality requires a complex approach, incorporating both technical measures and organizational policies. Techniques to ensure confidentiality include encryption, access control mechanisms, and data classification policies that dictate the levels of secrecy and the measures required to protect each classification level.</p><p>In procrastination-addressing applications, the integrity of data stands as a pillar of user trust and application efficacy. Integrity refers to the assurance that information is protected against unauthorized alteration or deletion and that it accurately reflects the original intended content as created, transmitted, or stored by the user. This principle ensures that the data presented and acted upon by both users and application algorithms remains true to its source, untainted by corruption or unauthorized manipulation. Integrity protection mechanisms include cryptographic hash functions, digital signatures, and version control systems. These measures help detect unauthorized changes, prevent data tampering, and ensure that data remains consistent, accurate, and valid over its entire lifecycle.</p><p>Availability, the third cornerstone of the CIA Triad, is pivotal for the functionality and reliability of digital solutions. Ensuring the availability of productivity applications involves a comprehensive strategy that incorporates redundancy, fault tolerance, regular maintenance, disaster recovery planning, load balancing, and vigilant monitoring. For applications targeting behavioral changes like procrastination, the uninterrupted availability is tightly linked to the application's ability to effectively support users in achieving their goals. Service interruptions not only impede user progress but can also foster frustration and reduce motivation, undermining the application's purpose <ref type="bibr" target="#b8">[9]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Security threats and vulnerabilities</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1.">Overview of common security threats</head><p>The cybersecurity area is continuously evolving, marked by an array of diverse and sophisticated threats. These threats, ranging from malware to sophisticated denial of service attacks, endanger the confidentiality, integrity, and availability of digital data.</p><p>Malware represents a significant threat, encompassing various forms of malicious software such as viruses, worms, and trojans. Viruses, for example, can replicate themselves and spread across networks, corrupting data and disrupting operations. Worms operate similarly but do not require human action to propagate, making them particularly virulent. Trojans disguise themselves as legitimate software, creating backdoors in security to facilitate further illicit activities. Each type of malware can cause extensive damage to digital systems, compromising both personal and corporate data.</p><p>Phishing Attacks leverage social engineering to deceive users into divulging sensitive information. These attacks typically occur through email, where attackers impersonate legitimate institutions to lure victims into entering personal data on fraudulent websites. Phishing is especially dangerous because it exploits human vulnerability, bypassing many technical safeguards.</p><p>Ransomware is a specific type of malware that encrypts a victim's files, demanding payment to restore access. These attacks directly impact data availability and can halt business operations, leading to significant financial losses and erosion of trust among users.</p><p>Denial of Service (DoS) and Distributed Denial of Service (DDoS) Attacks disrupt services by overwhelming systems with a flood of traffic. DoS attacks originate from a single source, whereas DDoS attacks are distributed across numerous compromised devices. These attacks aim to render websites and online services inoperative, causing operational disruption and damaging reputational trust.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2.">Security vulnerabilities and their implications for productivity applications</head><p>The evolution of the cybersecurity threat landscape poses significant challenges for productivity applications as well, as essential tools underpinning both individual productivity and organizational efficiency. These applications, encompassing a broad range of communication platforms to project management tools, serve as repositories for vast amounts of sensitive data, rendering them prime targets for cyber threats <ref type="bibr" target="#b1">[2]</ref>.</p><p>When attackers manipulate SQL queries to gain unauthorized access or modify a database, the consequences can be severe. This type of vulnerability not only leads to data breaches but also erodes user trust and can result in substantial legal and financial repercussions under data protection laws such as GDPR.</p><p>Furthermore, vulnerabilities that allow attackers to inject malicious scripts into web pages expose users to risks of sensitive information theft, such as session tokens. In environments where applications offer collaborative features, such security breaches can severely undermine the platform's credibility and reduce user confidence in the safety of their data.</p><p>Issues with authentication processes are equally concerning. Inadequate authentication mechanisms provide easy entry points for attackers, leading to unauthorized access and potential data leaks. The repercussions extend beyond data integrity, affecting user access and the overall reliability of the application. These disruptions are particularly detrimental in applications relied upon daily for personal management and productivity, directly impacting user satisfaction and trust.</p><p>The exposure of sensitive data due to insecure APIs or poor encryption practices can attract significant regulatory attention, resulting in heavy fines and damage to the organization's reputation. Moreover, operational disruptions from attacks like DDoS not only degrade service quality but can also lead to substantial downtime, frustrating users and compromising the effectiveness of the application.</p><p>To address these challenges, adopting a security-by-design approach throughout the application development lifecycle is critical. By implementing rigorous testing, compliance checks, and user education, developers can mitigate risks and reinforce the security framework of their applications. This proactive stance on security not only safeguards against specific vulnerabilities but also enhances user trust and compliance with international standards and regulations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Risk management in ISM</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1.">Risk assessment methodologies</head><p>Risk assessment is a fundamental aspect of information security management, providing a systematic process for identifying vulnerabilities and evaluating the risks associated with potential security threats. The methodologies employed in risk assessment can vary widely, each with its approach to quantifying and managing risk <ref type="bibr" target="#b11">[13]</ref>.</p><p>Risk assessments are generally categorized into two types: qualitative and quantitative. Qualitative assessments focus on subjective analysis of the impact and probability of risks based on expert opinion and industry knowledge. This type often results in risk prioritization on a scale such as low, medium, or high. Quantitative assessments, on the other hand, aim to assign numerical values to risks, calculating potential impacts in financial terms or other measurable units. This approach can provide a more objective basis for comparing risks and allocating resources <ref type="bibr" target="#b15">[17]</ref>.</p><p>Common Methodologies. OCTAVE (Operationally Critical Threat, Asset, and Vulnerability Evaluation): Developed by Carnegie Mellon University, OCTAVE is a framework that focuses on organizational risk and security practices. It is particularly suited for larger organizations looking to integrate business objectives with risk-based security strategies <ref type="bibr" target="#b4">[5]</ref>.</p><p>FAIR (Factor Analysis of Information Risk): FAIR is a quantitative risk assessment methodology that helps organizations understand, analyze, and quantify information risk in financial terms. It is useful for making informed decisions about security investments and risk management priorities <ref type="bibr" target="#b4">[5]</ref>.</p><p>Risk IT Framework: Designed by ISACA for IT-related risk, the Risk IT framework provides a comprehensive guide for enterprises to identify, govern, and manage IT risk. It helps organizations align IT risk management with overall enterprise risk management.</p><p>Adapting these methodologies to digital solutions involves considering the specific characteristics and requirements of the application. For instance, a digital tool designed to combat procrastination might utilize OCTAVE to assess organizational risks involving user data security and system availability. FAIR could be employed to quantify the financial impact of potential breaches or downtime, aiding in decision-making about where to focus security efforts. The Risk IT framework can guide the overall risk governance structure, ensuring that all IT risks are systematically managed in line with the application's strategic goals <ref type="bibr" target="#b19">[22]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2.">Identifying, prioritizing and mitigating risks</head><p>Effective risk management in digital applications requires identifying, prioritizing risks and implementing appropriate mitigation strategies. This integrated approach ensures that the most critical risks are addressed with effective solutions to protect the application and its users.</p><p>The first step in risk management is to identify potential risks. This involves a thorough analysis of the entire ecosystem of the digital application, including software components, user interactions, data flows, and external integrations. Techniques such as brainstorming sessions, expert interviews, and the use of automated tools can help uncover potential vulnerabilities. For digital applications aimed at combating procrastination, risks might include unauthorized access to user data, data leakage, or service interruptions that could derail users' productivity improvements <ref type="bibr" target="#b8">[9]</ref>.</p><p>Once identified, risks are prioritized based on their potential impact on the application and the likelihood of their occurrence. Tools such as risk matrices and SWOT analysis help in assessing risks to focus resources and attention on the most significant threats. Prioritization considers factors like the severity of impact, regulatory compliance requirements, and operational criticality.</p><p>The next crucial step is to implement strategies to mitigate those risks. Risk avoidance might be applied to eliminate threats, such as opting for more secure alternatives in technology or redesigning vulnerable system components. Where risks cannot be entirely avoided, reduction strategies are crucial and may include deploying advanced security measures like encryption, stringent access controls, and adherence to secure coding practices. In scenarios where risks cannot be internally managed, sharing through insurance or outsourcing to third-party vendors with specialized security expertise can be effective. Risk acceptance is considered for less critical risks, where the cost of mitigation exceeds the potential impact. Integral to these strategies are implementing robust preventative, detective, and corrective controls. Preventative controls are designed to prevent security incidents, detective controls to identify and react to incidents as they occur, and corrective controls to recover from incidents and restore normal operations. Continuous monitoring and regular review of these controls are essential to ensure they remain effective and are adjusted in response to evolving threats and business needs.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Security frameworks and standards</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1.">Overview of established frameworks</head><p>Established frameworks provide comprehensive guidelines and best practices for establishing, implementing, maintaining, and continually improving information security.</p><p>ISO/IEC 27001 is one of the most prevalent international standards for information security management systems (ISMS). It outlines a systematic approach to managing sensitive company information so that it remains secure. It includes people, processes, and IT systems by applying a risk management process. This standard is particularly useful for organizations that need to demonstrate their commitment to information security to clients or regulatory bodies through formal certification <ref type="bibr" target="#b5">[6]</ref>.</p><p>The NIST Cybersecurity Framework developed by the National Institute of Standards and Technology in the United States. The framework is used globally to improve cybersecurity across industries. It provides a policy framework of computer security guidance for organizations that want to assess and improve their ability to prevent, detect, and respond to cyber incidents. The NIST Framework is flexible and can be tailored to the specific needs of individual organizations, regardless of their size or sector <ref type="bibr">[19]</ref>.</p><p>COBIT is a comprehensive framework for IT governance and management developed by ISACA. It is designed to be a supportive tool for managers and allows for bridging the gap between technical issues, business risks, and control requirements. COBIT's principles and tools aim to provide a holistic approach to IT management, focusing on maximizing the value of information by aligning IT processes with business objectives.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2.">Application to procrastination-addressing digital solutions</head><p>Integrating established ISM frameworks and standards into digital solutions that focus on combating procrastination and enhancing productivity is critical for ensuring robust security while supporting functional and user-centric design. These frameworks provide a structured approach to safeguarding sensitive user data and maintaining application integrity, which are crucial for applications that handle personal productivity data.</p><p>Applications designed to manage procrastination often collect detailed data on user habits, preferences, and productivity patterns. Adhering to standards like ISO/IEC 27001 and the NIST Cybersecurity Framework helps ensure that this data is handled securely and responsibly. These frameworks provide guidelines for implementing comprehensive data protection measures that respect user privacy while preventing unauthorized access and data breaches <ref type="bibr" target="#b5">[6]</ref>.</p><p>Trust is a cornerstone of applications focused on personal productivity, as users need to feel confident that their sensitive data is in safe hands. Compliance with recognized security standards demonstrates a commitment to data protection, which can be a significant factor in user adoption and retention. For instance, aligning with GDPR and other privacy regulations not only meets legal requirements but also positions the application as trustworthy and reliable.</p><p>Digital solutions for procrastination need to be agile and responsive to changes in user behavior and technological advancements. Frameworks like COBIT can guide developers in managing IT risks that could affect the application's performance and security. These include risks from new software updates, integration with other apps, or evolving cyber threats. A structured risk management process enables developers to identify potential vulnerabilities early and adapt their security strategies accordingly. Procrastination-management applications benefit from a continuous improvement approach to security. This involves regular security audits, user feedback loops, and updates to security policies as part of the lifecycle management prescribed by frameworks like ISO/IEC 27001. Continuous improvement helps ensure that the application adapts to new security challenges and evolving user expectations, thus maintaining its effectiveness and competitive edge.</p><p>Evaluating security frameworks is essential for determining their suitability in addressing the unique requirements and challenges of procrastination-combatting applications. The Table <ref type="table" target="#tab_0">1</ref>. examines the effectiveness and applicability of established frameworks within the context of such applications, considering factors such as comprehensiveness, flexibility, and alignment with regulatory requirements.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Privacy and data protection</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.1.">Data protection laws</head><p>Data protection laws play a crucial role in safeguarding personal information, particularly for applications that collect and process user data to manage behaviors such as procrastination. Understanding these regulations is essential for ensuring legal compliance and safeguarding user privacy.</p><p>As one of the most stringent privacy and security laws in the world, the General Data Protection Regulation (GDPR) affects any entity that processes the data of EU citizens, regardless of the entity's location. For procrastination-addressing applications, this means adhering to principles of lawfulness, transparency, and consent. The GDPR mandates that users must explicitly consent to the collection and use of their data, which must be collected for specified, explicit, and legitimate purposes. Furthermore, users have the right to access their data, correct inaccuracies, and request the deletion of their data under certain circumstances <ref type="bibr">[12]</ref>.</p><p>California Consumer Privacy Act (CCPA) gives California residents the right to know what personal data is being collected about them, whether their personal data is sold or disclosed, and to whom. It also grants the right to object to the sale of personal data and the right to access their data. For apps focusing on productivity and procrastination, which might collect detailed user activity data, compliance involves implementing processes to manage user data access requests efficiently and transparently <ref type="bibr" target="#b9">[10]</ref>.</p><p>Depending on the nature of the procrastination management app, other specific laws might also apply. For instance, apps that integrate health tracking or mental well-being aspects might need to comply with the Health Insurance Portability and Accountability Act (HIPAA) in the U.S., which protects sensitive patient health information from being disclosed without the patient's consent or knowledge. Developers must also stay informed about emerging laws in other regions, such as Brazil's LGPD or India's proposed Personal Data Protection Bill, which introduce additional compliance requirements and could impact global operations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.2.">Relevance to digital solutions</head><p>Applications designed to manage procrastination often collect and analyze extensive personal data to provide customized advice and track user progress. The sensitivity of this data and the potential consequences of its misuse make robust data protection practices a fundamental requirement for these digital solutions.</p><p>Procrastination management applications typically gather data that users consider private, such as details about personal goals, daily routines, and behavioral patterns. This data can reveal much about a person's lifestyle, health, and psychological state. As such, protecting this information is a legal obligation under laws like GDPR and CCPA and also a critical aspect of maintaining user trust. Any breach that leads to unauthorized access could have severe repercussions, damaging the users' trust and the application's reputation.</p><p>Users of digital productivity tools have high expectations regarding the privacy and security of their data. They trust these applications to not only help them manage their time more effectively but also to protect the personal information they share. Failing to meet these expectations can lead to loss of trust, user attrition, and severe reputational damage.</p><p>The specific nature of data collected by procrastination-management apps increases their risk exposure, making them potential targets for cyber threats such as data breaches or unauthorized access. These risks are not only technical but also legal and ethical, as mishandling personal data can lead to significant legal repercussions under laws like GDPR or CCPA.</p><p>Non-compliance with data protection laws can result in hefty fines and legal actions. Beyond the financial implications, non-compliance can erode user confidence, impacting the application's marketability and long-term viability. For instance, a breach in user data privacy can trigger a decline in user engagement, negatively affecting the overall effectiveness of the app in managing procrastination.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.3.">Compliance strategies</head><p>Ensuring compliance with data protection laws is critical for applications that help users manage procrastination. These laws not only protect users but also build trust and enhance the credibility of digital solutions.</p><p>Procrastination-combatting digital solutions should adopt a data minimization approach, collecting only the necessary information required for their functionality. By limiting data collection to essential elements, such as preferences or task schedules, these applications can minimize the potential impact of data breaches and unauthorized access.</p><p>Moreover, implementing robust user consent mechanisms is paramount to ensuring compliance with privacy regulations. Procrastination-combatting apps should obtain explicit consent from users before collecting, processing, or sharing their data. Transparent disclosure of data practices and clear opt-in/opt-out options empower users to make informed decisions about their data usage, fostering trust and accountability.</p><p>Incorporating privacy by design principles into the development process is integral to building privacy-centric procrastination-combatting solutions. By embedding privacy considerations into every stage of product design and development, from concept ideation to deployment, developers can proactively address privacy risks and vulnerabilities. Privacy-enhancing features, such as end-to-end encryption and anonymization techniques, should be prioritized to safeguard user data against unauthorized access and misuse.</p><p>Ongoing compliance monitoring and auditing are essential components of an effective privacy and data protection strategy. Procrastination-combatting app developers should establish internal processes for regularly assessing compliance with relevant regulations, conducting privacy impact assessments, and maintaining comprehensive audit trails. External audits by independent third-party assessors can provide additional validation of compliance efforts, demonstrating a commitment to transparency and accountability.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.4.">Designing security requirements for a procrastination-addressing digital solution</head><p>This document outlines the security requirements for a prototype of a mobile application designed to combat procrastination issue through gamification and task management (Fig. <ref type="figure" target="#fig_0">1</ref>). The objective is to develop a security framework that not only protects user data but also aligns with global security standards, ensuring the application's integrity and trustworthiness.</p><p>The security requirements specified in this document are structured to provide a comprehensive approach to safeguard the application from inception through deployment and operation. Inspired by the OWASP Mobile Application Security Verification Standard (MASVS), this work aligns with globally recognized best practices tailored specifically to the mobile environment <ref type="bibr" target="#b13">[15]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Architecture, design, and threat modeling</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.1.">Architecture and design</head><p>The prototype is conceptualized to engage users with a dynamic interface that helps manage tasks effectively while encouraging progress through gamified elements. As a prototype aimed at demonstrating potential functionalities and security strategies, it incorporates best practices in software architecture and mobile application security.</p><p>The architecture of the digital solution encompasses multiple layers, each serving distinct functions while contributing to the overall security and usability of the application.</p><p>At the presentation layer, the use of frameworks like React Native or Flutter ensures a responsive and engaging user interface across different mobile platforms. This layer is meticulously designed to handle user inputs, display task-related information, and manage interactive elements with a focus on usability and accessibility.</p><p>Beneath the presentation layer lies the business logic layer, where the core functionalities of the application reside. This layer processes user requests, manages task data, and orchestrates gamification features to incentivize user engagement and productivity. Hosted on a secure cloud platform, the business logic layer leverages cloud-native services and best practices to ensure scalability, reliability, and resilience against potential security threats.</p><p>The data storage layer, situated at the foundation of the architecture, is responsible for persistently storing user data, task-related information, and application settings. Utilizing encrypted database solutions, this layer employs industry-standard encryption algorithms and access control mechanisms to safeguard sensitive data from unauthorized access and malicious tampering. Additionally, data integrity checks and redundancy measures are implemented to mitigate the risk of data corruption or loss.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.2.">Threat modeling</head><p>Threat modeling is a crucial step in identifying and assessing potential security risks to our procrastination-addressing digital solution. Each category of threat identified by STRIDE is analyzed to determine its potential impact on the system and the likelihood of its occurrence. This detailed analysis informs the prioritization and resource allocation for security measures <ref type="bibr" target="#b7">[8]</ref>.</p><p>In the digital solution, spoofing identity refers to the risk where unauthorized individuals may attempt to gain access to the system by impersonating legitimate users. This could occur through phishing attacks where attackers deceive users into providing their login credentials. The likelihood of such incidents is considered medium given the common nature of these tactics despite robust authentication mechanisms. The impact, however, is high as successful spoofing attacks could lead to unauthorized access to sensitive user data and personal information, severely undermining user trust and data integrity. To mitigate this risk, implementing multi-factor authentication and conducting regular security awareness training for users are essential steps. Prioritizing these measures is critical due to the high potential impact on the system's integrity and user privacy.</p><p>Tampering involves unauthorized alterations to data or system configurations. Within the productivity-combatting application, this might manifest as unauthorized changes to user-set tasks or personal goals, potentially through cross-site scripting (XSS) or SQL injection attacks where attackers inject malicious code into the system. The likelihood of tampering is low due to stringent input validation and access controls. However, the impact of such an event is high as it could corrupt the accuracy of user data and disrupt the application's functionality. Ensuring data integrity is therefore a medium priority, with continuous implementation of secure coding practices, regular code reviews, and comprehensive access control mechanisms as our primary defences <ref type="bibr" target="#b1">[2]</ref>.</p><p>Information disclosure poses a significant threat to this application, especially concerning the unauthorized access to or exposure of personal user data through breaches or leaks. The likelihood of this threat is high, as data breaches continue to be prevalent in the digital landscape, often through compromised security systems or insider threats. The impact is deemed very high due to the potential for severe privacy violations and subsequent legal and reputational damage. Consequently, this threat is a very high priority, and robust measures, including advanced encryption, comprehensive data access policies, etc.</p><p>A Denial of Service (DoS) attack aims to make the digital solution unavailable to legitimate users, typically by overwhelming the system with excessive requests. The likelihood of such attacks is medium, reflecting the general risk across digital platforms. The impact is also medium, as service disruptions can degrade user experience but usually do not result in permanent damage. Mitigating DoS attacks is a medium priority, with strategies such as deploying anti-DDoS protections and ensuring scalability and redundancy in our hosting infrastructure.</p><p>Elevation of privilege involves attackers gaining higher-level permissions than intended, allowing them to execute actions that should be restricted. While the likelihood of this occurring is low due to stringent access controls, the potential impact is very high as it could lead to extensive unauthorized access and system damage. Preventing such escalation is a high priority, necessitating rigorous enforcement of the principle of least privilege, regular audits of user permissions, and the deployment of anomaly detection systems to quickly identify unauthorized attempts to elevate privileges. Table <ref type="table" target="#tab_1">2</ref> below presents a summary of key threats identified along with their potential impact, likelihood, priority, and corresponding mitigation strategies. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.">Data storage and privacy</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.1.">Data management</head><p>Effective data management is fundamental to the development of the prototype mobile application.</p><p>Given the diverse range of user-generated content and operational data involved, adopting a systematic approach to data collection, storage, and processing is crucial. This approach must align with global data protection standards, particularly the General Data Protection Regulation <ref type="bibr">[12]</ref>, to ensure the privacy and security of user data, especially for potential users within the European Union <ref type="bibr" target="#b16">[18]</ref>.</p><p>In the context of data collection and classification, the application will only collect essential data required for delivering its services. This includes personal information for account setup, task details for functionality, and interaction data for enhancing user experience. Personal information, such as names and email addresses, will be gathered with explicit user consent, accompanied by clear explanations regarding the purposes and benefits of data submission. Task details, including deadlines and notes, will be treated with utmost confidentiality due to their personal nature. Additionally, data on user interactions with the application's features will be handled judiciously to maintain user privacy while leveraging insights to refine functionality.</p><p>To ensure the security of data storage and access, the application will leverage encrypted cloud services, employing robust encryption protocols such as Advanced Encryption Standard (AES-256) for data at rest and Transport Layer Security (TLS) for data in transit. Role-Based Access Control (RBAC) will be implemented to regulate data access within the application, with strict user permission policies based on predefined roles to prevent unauthorized data access.</p><p>Data retention and compliance are also critical considerations. The application will adhere to a concise data retention policy, limiting the duration of stored data to what is strictly necessary for its intended purposes. Users will have control over their data management, including the ability to update or delete their information, empowering them to maintain control over their data. Furthermore, the application will be designed to comply with relevant privacy laws, incorporating mechanisms to address user rights under GDPR, such as data portability and the right to erasure <ref type="bibr" target="#b12">[14]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.2.">Privacy enhancements</head><p>Data anonymization serves as a critical method in protecting user privacy, especially when handling data that could reveal personal user behaviors or preferences. In the prototype, anonymization is applied to user interaction data, which includes general metrics on app usage patterns and feature engagement. This data is processed to remove or obscure any personally identifiable information (PII), employing techniques such as pseudonymization and aggregation <ref type="bibr" target="#b18">[21]</ref>.</p><p>Pseudonymization replaces identifiers with pseudonyms, severing the direct link between data sets and user identities, while aggregation combines data points from multiple users to create a nonidentifiable dataset that prevents the reverse engineering of individual profiles. These measures significantly reduce the risk of privacy breaches and ensure that the data used for improving app functionalities and conducting analytics cannot be traced back to any individual user.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.">Cryptography requirements</head><p>The implementation of robust cryptographic measures is paramount, as it helps securing user data and ensuring that communications between the application and its servers are shielded against interception and tampering. The application will incorporate advanced encryption protocols to safeguard data at every stage of its lifecycle: Data Encryption at Rest: Given the sensitive nature of personal and task-related information, the application will employ the Advanced Encryption Standard (AES) with a 256-bit key for encrypting data stored within its databases and on user devices. AES-256 is renowned for its robustness, and a meticulous key management system, including hardware security modules (HSMs) and key rotation procedures, will be implemented to securely manage encryption keys <ref type="bibr" target="#b14">[16]</ref>.</p><p>Data Encryption in Transit: Transport Layer Security (TLS) version 1.3 will be utilized for encrypting all data transmitted between the mobile application and the server. TLS 1.3 offers improved security and efficiency, ensuring that data in transit remains confidential and unaltered. The application will enforce HTTPS across all API endpoints to guarantee encrypted communication channels.</p><p>The prototype will leverage cryptographic hash functions, incorporating salted hashes to enhance the security of stored credentials. Salted hashes prevent attackers from efficiently using precomputed tables (e.g., rainbow tables) to crack passwords, significantly bolstering the application's security posture <ref type="bibr" target="#b10">[11]</ref>.</p><p>For sensitive operations like financial transactions, the application will employ challengeresponse authentication mechanisms. This approach safeguards against man-in-the-middle attacks by ensuring that intercepted communications do not expose reusable credentials.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.1.">Authentication and session management</head><p>Effective authentication and session management are fundamental to securing user interactions within mobile applications. These mechanisms not only verify user identities but also ensure that users are authorized to perform actions within their sessions without compromising security. For the mobile application prototype focused on reducing procrastination and gamification, implementing robust authentication and reliable session management is imperative to protect against unauthorized access and session hijacking.</p><p>To strengthen the authentication process, the prototype will require users to provide multiple forms of verification. This includes SMS-based verification, the use of authentication apps and backup codes. MFA significantly reduces the risk of unauthorized access even if one credential component is compromised.</p><p>Depending on the sensitivity of the actions being performed or the user's login behavior, the system may invoke additional security checks. For instance, if a login attempt is made from a new device or location, the system will prompt for additional verification steps or send an alert to the user's primary email. The prototype will enforce strong password policies requiring users to create passwords with a mix of characters, numbers, and symbols. Passwords will be stored using salted hash functions to ensure that stored credentials are not in plain text. Additionally, the prototype will integrate features for password recovery and reset that are secure and user-friendly.</p><p>Maintaining the integrity and security of user sessions is crucial to preventing session-related attacks such as session hijacking and fixation:  Sessions will have an automatic timeout limit to reduce the risk of unauthorized access when devices are left unattended. For sessions requiring extended duration, periodic re-authentication will be necessary, especially before accessing sensitive features or data.  Session tokens will be generated using cryptographic methods to ensure they are unique and cannot be guessed or reused. These tokens will be securely stored on the device and validated on the server for each session-related request.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head></head><p>Proper session termination practices will be implemented to ensure that sessions are securely ended when users log out or after periods of inactivity. This includes invalidating session tokens both client-side and on the server. To ensure that the authentication and session management systems remain secure against emerging threats, the prototype will undergo regular security reviews and updates. This includes updating authentication protocols and session management strategies to incorporate new security practices and respond to new vulnerabilities discovered in the technology landscape.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.2.">Platform interaction</head><p>In the design of digital solutions aimed at combating procrastination, understanding the user and system interactions is paramount to identifying potential security risks. The prototype involves complex interactions where users manage tasks, engage socially, and earn rewards based on their activities. Table <ref type="table" target="#tab_2">3</ref> below categorizes the different types of user interactions within the application, identifying potential security risks and proposing mitigation strategies for each interaction type.</p><p>The core functionalities where user interaction is most prevalent include account creation and management, task management, social interactions, and the reward system. Each interaction point involves specific data points such as emails, usernames, passwords, task descriptions, and personal details, which are susceptible to various security threats. For instance, account creation and management are critical areas vulnerable to account takeovers and data breaches. This necessitates robust security measures such as CAPTCHA, two-factor authentication (2FA), and rate limiting to prevent unauthorized access and safeguard user information. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.3.">Implementing and evaluating security measures for a prototype in Figma</head><p>The primary objective of our work is to implement and evaluate the security measures designed within a digital solution prototype to combat procrastination. This work bridges theoretical security planning and practical application, showcasing how advanced security protocols can seamlessly integrate into a user-centric digital environment. The focus is on enhancing the prototype's security while maintaining ease of use and ensuring compliance with relevant data protection laws. The prototype, designed using Figma, simulates a mobile application that provides task management tools enhanced with social features to engage users in a productive and secure environment. The prototype includes detailed user interaction flows for registration, authentication, account management, and privacy settings, emphasizing robust security measures such as multifactor authentication (MFA), data encryption, and compliance with the General Data Protection Regulation (GDPR).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.4.">Registration and authentication flow</head><p>The registration and login processes are designed to ensure user identity verification while maintaining a balance between security and user convenience. These processes are critical for preventing unauthorized access and protecting user data from potential security breaches.</p><p>The application supports various authentication methods to cater to user preferences and security needs. This includes traditional email/password combinations and more seamless integrations with third-party authentication providers like Google and GitHub. Figure <ref type="figure" target="#fig_1">2</ref>. below provides a more detailed visual presentation of this process.</p><p>For third-party authentication providers, the application uses OAuth, a widely accepted open standard for access delegation. It allows users to grant websites or applications access to their information on other websites but without giving them the passwords. This is particularly useful for enhancing user experience by simplifying the login process and reducing password fatigue.</p><p>All data transmitted during the registration and login processes is encrypted using SSL/TLS, ensuring that user credentials and other sensitive information are securely transmitted over the internet. MFA adds an additional layer of security by requiring two or more verification factors, which significantly decreases the risk of unauthorized access. The application provides several options for MFA, each designed to meet different user needs and security levels. The visual process is presented in the Figure <ref type="figure" target="#fig_2">3</ref>. SMS-based Verification. Users receive a one-time password (OTP) via SMS, which they must enter in addition to their regular password. This method is widely used due to its simplicity and relatively strong security profile. The system utilizes a reliable SMS gateway provider to ensure timely delivery of OTPs. This method leverages the user's access to a mobile device as a form of something they have, adding a physical layer of security. SMS-based OTP is popular and widely understood by users, making it a practical choice for initial MFA implementation.</p><p>Authentication App (e.g., Google Authenticator). Recommended for users seeking higher security, this method involves generating a time-based OTP through an app installed on the user's smartphone. The application uses a Time-Based One-Time Password (TOTP) algorithm, which creates a new password at fixed intervals, ensuring that each password is only valid for a short period. Unlike SMS, which can be intercepted, TOTP requires physical access to the user's smartphone, providing a higher level of security.</p><p>Backup Codes. As a fallback mechanism, users can generate a set of backup codes during MFA setup. These codes can be used to access the account if the primary MFA method is unavailable. Backup codes are designed to be used sparingly and securely stored by the user. They are generated in the app and can be printed or saved offline for emergency use. Two-factor authentication can be enabled and setup in the security settings, where users can choose their preferred MFA method. The interface guides them through the setup process for each option. Each time the user logs in, after entering their password, the system prompts them to complete the second factor of authentication based on their chosen method.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.5.">Password and security management</head><p>Password and security management are essential components of maintaining robust account security. This section of the application allows users to control and secure their account credentials and settings, providing tools for password changes, recovery options, and managing other security-related preferences.</p><p>Password Change allows users to update their password regularly, which is a fundamental practice in maintaining account security. The system employs a password strength validator to ensure that users create strong, hard-to-guess passwords. This tool checks for minimum length, the inclusion of special characters, numbers, and mixed-case letters. Passwords are never stored as plain text. They are hashed using a secure hash algorithm, enhancing the security of stored credentials even in the event of a data breach.</p><p>In case users forget their passwords, the application provides a secure method to regain access to their accounts. Users can request a password reset link sent to their registered email or SMS, depending on their security preferences. This process includes verification steps to ensure that only the rightful account owner can reset the password. To prevent abuse, the password reset feature is equipped with rate limiting, reducing the risk of brute force attacks aiming to guess or reset passwords maliciously.</p><p>Users can review and adjust their MFA settings, enabling or disabling MFA methods according to their security needs. A dedicated section within the security settings allows users to toggle on or off different MFA options, view their current configurations, and set up new methods if necessary.</p><p>Session Management provides a control panel for users to see all active sessions across different devices, offering the ability to end sessions that they do not recognize or no longer need. Each session is uniquely identified and displayed with information such as device type, location (if available), and last active time. This helps users manage their sessions effectively. Users can instantly log out from any device remotely, enhancing security in case a device is lost or stolen. The implementation of security measures as password resetting involves creating intuitive and secure interfaces where users can easily manage their password and security settings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="9.6.">Data privacy management</head><p>Data privacy management is a critical component that empowers users to control their personal information within the application. This area focuses on ensuring users can exercise their rights over their data, in compliance with data protection laws such as GDPR. It includes managing data sharing preferences, handling data access requests, and ensuring transparent communication regarding data usage.</p><p>Privacy Settings Dashboard centralizes all privacy-related settings, making it easy for users to understand and manage their data privacy preferences. The dashboard is designed to offer a clear overview of privacy settings, including data sharing options and access rights, with easy-to-navigate sections and descriptive icons. Information displayed is dynamically adjusted based on user settings and preferences, ensuring users receive relevant and personalized information.</p><p>Privacy Policy allows users to view the data the application has collected about them and to request a copy in a portable format for transparency and control over their information. It is extremely important to ensure that all data handling processes are secure, minimizing the risk of unauthorized access during the data retrieval process. Users are able to to request the deletion of their account and associated data, aligning with the "right to be forgotten".</p><p>Another security feature implemented is Login Alerts, with which users can preferences for how they receive notifications about unrecognized logins-either through in-app notifications, emails, or both. Alerts are integrated with the user's account settings, allowing for easy adjustments anytime. Moreover, Automated Checkup offers automated recommendations for users to enhance their account security, such as updating passwords, verifying email addresses, and confirming phone numbers are correct. It provides interactive tips and direct links to update security settings, making it easy for users to follow through on recommendations.</p><p>Device Permissions Features is a dedicated section within the app settings that allows users to see at a glance all the permissions the app has requested and to toggle these permissions on or off. The dashboard is structured to provide a clear and concise overview of all device permissions, such as camera, microphone, location, and contacts. Each permission is accompanied by an explanation of why it is needed, enhancing user trust and compliance with privacy practices. The app uses system APIs to request permissions only when necessary, following the principle of least privilege. Permissions can be toggled on or off depending on user preference, with the app responding accordingly by enabling or disabling specific features.</p><p>Users can manage permissions individually, providing them with the ability to tailor the app's access to only those functionalities they are comfortable with. Permissions are requested in context, meaning the app asks for permission at the point when access to a device feature is necessary, which can help reduce user concerns about privacy.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="10.">Conclusions</head><p>1. This initial phase successfully laid the foundational groundwork for understanding the complex landscape of information security within digital solutions aimed at combating procrastination. By exploring various security frameworks, threat modeling, and risk management techniques, the assignment provided a thorough theoretical backdrop against which practical security measures can be developed and implemented. It emphasized the importance of robust information security management to safeguard sensitive user data and maintain trust in digital applications. The insights gained serve as the basis for the subsequent practical applications, ensuring a well-informed approach to designing secure digital solutions.</p><p>2. Building on the theoretical knowledge, this phase applied these concepts to design detailed security requirements for the prototype of a digital solution focused on enhancing productivity through procrastination management. Covering critical aspects of security such as authentication, data privacy, session management, and compliance with legal standards like GDPR, the work not only addressed potential vulnerabilities identified through threat modeling but also set a solid framework for implementing these security features practically. This comprehensive approach ensures that the prototype is not only functional but also secure from various cybersecurity threats.</p><p>3. The final phase brought the theoretical designs and security requirements to life through practical implementation within a digital solution prototype. Detailing the integration of security measures into the prototype demonstrated the feasibility and effectiveness of the security strategies in a simulated real-world environment. This work provided insights into the challenges of implementing security features and solutions to enhance user experience without compromising security. Moreover, it showcased how security and functionality can be balanced effectively, paving the way for potential future development and real-world application of the prototype.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Information Architecture.</figDesc><graphic coords="8,82.08,576.74,436.13,187.80" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Registration process flow.</figDesc><graphic coords="14,76.55,62.35,447.60,185.99" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Two-factor authentication.</figDesc><graphic coords="14,77.58,344.48,445.05,161.99" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc></figDesc><table><row><cell cols="2">Frameworks Comparison</cell><cell></cell><cell></cell></row><row><cell>Framework</cell><cell>Focus Area</cell><cell>Key Features</cell><cell>Applicability to</cell></row><row><cell></cell><cell></cell><cell></cell><cell>Procrastination-</cell></row><row><cell></cell><cell></cell><cell></cell><cell>Combatting Apps</cell></row><row><cell>ISO/IEC 27001</cell><cell>Comprehensive</cell><cell>Systematic approach, risk</cell><cell>High -versatile for all</cell></row><row><cell></cell><cell>ISMS</cell><cell>management, control</cell><cell>app types</cell></row><row><cell></cell><cell></cell><cell>implementation</cell><cell></cell></row><row><cell>NIST</cell><cell>Cybersecurity risk</cell><cell>Core functions (Identify,</cell><cell>Medium -ideal for</cell></row><row><cell>Cybersecurity</cell><cell>management</cell><cell>Protect, Detect, Respond,</cell><cell>critical infrastructure</cell></row><row><cell></cell><cell></cell><cell>Recover), tailored to</cell><cell>apps</cell></row><row><cell></cell><cell></cell><cell>organizational needs</cell><cell></cell></row><row><cell>COBIT</cell><cell>IT governance and</cell><cell>Aligns IT with business</cell><cell>Low -more suitable</cell></row><row><cell></cell><cell>management</cell><cell>goals, ensures compliance,</cell><cell>for enterprise IT</cell></row><row><cell></cell><cell></cell><cell>optimizes resources</cell><cell>management</cell></row><row><cell>PCI DSS</cell><cell>Payment card data</cell><cell>Secure data processing,</cell><cell>Medium -essential for</cell></row><row><cell></cell><cell>security</cell><cell>strong access control,</cell><cell>apps handling</cell></row><row><cell></cell><cell></cell><cell>network infrastructure</cell><cell>payments</cell></row><row><cell></cell><cell></cell><cell>security</cell><cell></cell></row><row><cell>GDPR</cell><cell>Data protection and</cell><cell>Data subject rights, data</cell><cell>High -mandatory for</cell></row><row><cell></cell><cell>privacy</cell><cell>protection principles,</cell><cell>apps used by EU</cell></row><row><cell></cell><cell></cell><cell>regulatory compliance</cell><cell>residents</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2</head><label>2</label><figDesc></figDesc><table><row><cell>Threat Analysis</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Threat</cell><cell>Impact</cell><cell cols="2">Likelihood Priority</cell><cell>Mitigation Strategy</cell></row><row><cell>Spoofing Identity</cell><cell>High</cell><cell>Medium</cell><cell>High</cell><cell>Multi-factor authentication, security</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>awareness training</cell></row><row><cell>Tampering with Data</cell><cell>High</cell><cell>Low</cell><cell>Medium</cell><cell>Input validation and parameterized</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>queries, least privilege access controls</cell></row><row><cell>Repudiation</cell><cell>Medium</cell><cell>Medium</cell><cell>Medium</cell><cell>Content security policies, sanitize user</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>input to prevent script injection</cell></row><row><cell>Information Disclosure</cell><cell>Very High</cell><cell>High</cell><cell>Very High</cell><cell>Advanced encryption, enforce data access policies, conduct continuous monitoring</cell></row><row><cell>Denial of Service</cell><cell>Medium</cell><cell>Medium</cell><cell>Medium</cell><cell>Anti-DDoS protections, ensure scalability</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>and redundancy</cell></row><row><cell>Elevation of Privilege</cell><cell>Very</cell><cell>Low</cell><cell>High</cell><cell>Principle of least privilege, regular audits,</cell></row><row><cell></cell><cell>High</cell><cell></cell><cell></cell><cell>anomaly detection systems</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>Table 3</head><label>3</label><figDesc>User and System Interaction Analysis</figDesc><table><row><cell>Interaction</cell><cell>Description</cell><cell>Data Points</cell><cell cols="2">Security Concerns Mitigation Strategies</cell></row><row><cell>Type</cell><cell></cell><cell></cell><cell></cell><cell></cell></row><row><cell>Account</cell><cell>Users create</cell><cell>Email,</cell><cell>Vulnerable to</cell><cell>Implement</cell></row><row><cell>Creation and</cell><cell>accounts and</cell><cell>username,</cell><cell>account takeover,</cell><cell>CAPTCHA, two-</cell></row><row><cell>Management</cell><cell>manage profiles</cell><cell>password,</cell><cell>and data breaches</cell><cell>factor authentication</cell></row><row><cell></cell><cell></cell><cell>personal details</cell><cell></cell><cell>(2FA), and rate</cell></row><row><cell></cell><cell></cell><cell></cell><cell></cell><cell>limiting</cell></row><row><cell>Task</cell><cell>Users input and</cell><cell>Task</cell><cell>Unauthorized</cell><cell>Use data validation</cell></row><row><cell>Management</cell><cell>manage tasks</cell><cell>descriptions,</cell><cell>access, and data</cell><cell>and user</cell></row><row><cell></cell><cell></cell><cell>categories,</cell><cell>manipulation risks</cell><cell>authentication to</cell></row><row><cell></cell><cell></cell><cell>deadlines</cell><cell></cell><cell>secure access</cell></row><row><cell>Social</cell><cell>Users participate</cell><cell>Messages, group</cell><cell>Harassment,</cell><cell>Content filtering,</cell></row><row><cell>Interaction</cell><cell>in groups, chat,</cell><cell>memberships,</cell><cell>spreading of</cell><cell>user reporting, and</cell></row><row><cell></cell><cell>and challenges</cell><cell>interactions</cell><cell>malware, privacy</cell><cell>blocking</cell></row><row><cell></cell><cell></cell><cell></cell><cell>breaches</cell><cell>mechanisms</cell></row><row><cell>Reward</cell><cell>Users earn and</cell><cell>Points, item</cell><cell>Exploitation of</cell><cell>Monitor for unusual</cell></row><row><cell>System</cell><cell>spend points on</cell><cell>purchases,</cell><cell>reward</cell><cell>activity, and validate</cell></row><row><cell></cell><cell>virtual goods</cell><cell>reward history</cell><cell>mechanisms, unfair</cell><cell>transactions server-</cell></row><row><cell></cell><cell></cell><cell></cell><cell>manipulation</cell><cell>side</cell></row></table></figure>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Declaration on Generative AI</head><p>The authors have not employed any Generative AI tools.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Cyber Security Challenges and its Emerging Trends on Latest Technologies</title>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">M</forename><surname>Rajasekharaiah</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IOP Conference Series: Materials Science and Engineering</title>
		<imprint>
			<biblScope unit="volume">981</biblScope>
			<biblScope unit="page">22062</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Specification, detection, and treatment of STRIDE threats for software components: Modeling, formal methods, and tool support</title>
		<author>
			<persName><forename type="first">Q</forename><surname>Rouland</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Hamid</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Jaskolka</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Systems Architecture</title>
		<imprint>
			<biblScope unit="volume">117</biblScope>
			<biblScope unit="page">102073</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Cyber Security Threats and Countermeasures in Digital Age</title>
		<author>
			<persName><forename type="first">M</forename><surname>Thakur</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Applied Science and Education (JASE)</title>
		<imprint>
			<biblScope unit="volume">04</biblScope>
			<biblScope unit="issue">01</biblScope>
			<biblScope unit="page" from="1" to="20" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Toward a Better Understanding of -Cybersecurity‖</title>
		<author>
			<persName><forename type="first">J</forename><surname>Van Der Ham</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Digital Threats: Research and Practice</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">3</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
	<note>Article 18</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Securing Cisco IP Telephony Networks</title>
		<ptr target="https://www.ciscopress.com/articles/article.asp?p=2803867&amp;seqNum=4" />
		<imprint>
			<date type="published" when="2017-10-03">2017. October 3</date>
			<publisher>Cisco Press</publisher>
		</imprint>
		<respStmt>
			<orgName>Cisco</orgName>
		</respStmt>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<idno>ISO/IEC 27001</idno>
		<ptr target="https://www.iso.org/standard/27001" />
		<title level="m">Information technology -Security techniques -Information security management systems -Requirements</title>
				<imprint>
			<publisher>International Organization for Standardization</publisher>
			<date type="published" when="2022">2022. 2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Information Security Requirement: The Relationship Between Confidentiality, Integrity and Availability in Digital Social Media</title>
		<author>
			<persName><forename type="first">S</forename><surname>Al-Janabi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Al-Shourbaji</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Information Security Theory and Practice</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2021">2021</date>
			<biblScope unit="page" from="289" to="305" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Methods, methodologies, and tools for threat modeling with case study</title>
		<author>
			<persName><forename type="first">A</forename><surname>Hajrić</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Smaka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Baraković</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Baraković Husić</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Telfor Journal</title>
		<imprint>
			<biblScope unit="volume">12</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Information Security Requirement: The Relationship Between Cybersecurity Risk Confidentiality, Integrity and Availability in Digital Social Media</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">Z</forename><surname>Khidzir</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">A M</forename><surname>Daud</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Ismail</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">S A A</forename><surname>Ghani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A H</forename><surname>Ibrahim</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Regional Conference on Science, Technology and Social Sciences</title>
				<meeting><address><addrLine>RCSTSS; Singapore</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016">2018. 2016</date>
			<biblScope unit="page" from="229" to="237" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<ptr target="https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?division=3.&amp;part=4.&amp;lawCode=CIV&amp;title=1.81" />
		<title level="m">Civil Code -CIV</title>
				<imprint>
			<publisher>California Legislative Information</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<author>
			<persName><forename type="first">Daisie</forename><surname>Team</surname></persName>
		</author>
		<ptr target="https://blog.daisie.com/cryptography-for-mobile-app-security-5-ways/" />
		<title level="m">Cryptography for Mobile App Security: 5 Ways. Daisie</title>
				<imprint>
			<date type="published" when="2023-08-07">2023. August 7</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">The process of risk management needs to evolve with the changing technology in the digital world</title>
		<author>
			<persName><forename type="first">O</forename><forename type="middle">K</forename><surname>Hussain</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2022-08-12">2022. 12 August 2022</date>
			<publisher>Springer Nature</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Before and after GDPR: tracking in mobile apps</title>
		<author>
			<persName><forename type="first">K</forename><surname>Kollnig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Binns</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Van Kleek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Lyngs</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Zhao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Tinsman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Shadbolt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Internet Policy Review</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">4</biblScope>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><surname>Owasp</surname></persName>
		</author>
		<ptr target="https://mas.owasp.org/MASVS" />
		<title level="m">Mobile Application Security Verification Standard (MASVS) (Version 2.1.0</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note>OWASP MASVS</note>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Mobile App Cryptography</title>
		<author>
			<persName><surname>Owasp</surname></persName>
		</author>
		<ptr target="https://mas.owasp.org/MASTG/General/0x04g-Testing-Cryptography/" />
	</analytic>
	<monogr>
		<title level="m">OWASP Mobile Application Security Testing Guide (MASTG)</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Information Security Risk Assessment</title>
		<author>
			<persName><forename type="first">I</forename><surname>Kuzminykh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Ghita</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Sokolov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Bakhshi</surname></persName>
		</author>
		<idno type="DOI">10.3390/encyclopedia1030050</idno>
		<ptr target="https://doi.org/10.3390/encyclopedia1030050" />
	</analytic>
	<monogr>
		<title level="j">Encyclopedia</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="602" to="617" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<author>
			<persName><forename type="first">T</forename><surname>Lambert</surname></persName>
		</author>
		<ptr target="https://pdtn.org/personal-data-protection-in-mobile-apps/" />
		<title level="m">Personal Data Protection in Mobile Apps: Best Practices and Guidelines</title>
				<imprint>
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Guide for conducting risk assessments</title>
		<author>
			<persName><surname>Nist</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">NIST SP 800-30 R1</title>
				<imprint>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="800" to="830" />
		</imprint>
	</monogr>
	<note>Revision 1</note>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<ptr target="https://iapp.org/resources/article/guide-to-basic-data-anonymization-techniques/" />
		<title level="m">Guide to Basic Data Anonymization Techniques</title>
				<imprint>
			<publisher>PDPC</publisher>
			<date type="published" when="2018-01-25">2018. January 25</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<author>
			<persName><forename type="first">B</forename><surname>Tucker</surname></persName>
		</author>
		<ptr target="https://insights.sei.cmu.edu/blog/octave-forte-and-fair-connect-cyber-risk-practitioners-with-the-boardroom/" />
		<title level="m">OCTAVE® FORTE and FAIR Connect Cyber Risk Practitioners with the Boardroom</title>
				<imprint>
			<date type="published" when="2018-06-21">2018. June 21</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
