Unit-3 (CS)
Unit-3 (CS)
Security
UNIT-III
Web and Mobile Security
1. Fundamental Concepts and Approaches
2. Sandboxing,
3. Client-Side and Server-Side Vulnerabilities
4. Mitigations.
1. Fundamental Concepts and
Approaches
I. Appification
II. Webification
III. Application Stores
I. Appification
• Definition: Appification refers to the shift from web-based platforms
to mobile applications for accessing online content.
• Impact: It has changed how software is produced, distributed, and
consumed, making mobile devices the primary interface for web
access.
• Security Concerns: The rise of appification has led to increased client-
side security challenges. Many apps use backend services for
computation and storage, which can introduce vulnerabilities.
• Citizen Developers: Non-professional developers often create apps
using easy-to-use tools, leading to security issues such as
reconfiguration and code injection attacks.
II. Webification
• Definition: Webification refers to the use of web technologies (e.g.,
JavaScript, Python, Ruby) in building applications for web browsers
and mobile web applications.
Key Technologies:
• Uniform Resource Locators (URLs): URLs are used to locate and
access web resources. Various segments, such as scheme, host, and
resource path, make up a URL.
The syntax of an absolute URL is:
scheme://credentials@host:port/resourcepath?
query_parameters#fragments.
URL segments
• Hypertext Transfer Protocol (HTTP): HTTP is the protocol used to exchange
web documents. It supports features like cookies for session management.
• Hypertext Markup Language (HTML): HTML is the language used to create
web documents. Proper HTML syntax is crucial to avoid web security issues
like cross-site scripting (XSS).
• Cascading Style Sheets (CSS): CSS is used to style HTML documents. Security
issues may arise when user-controlled values are improperly handled.
• JavaScript: A powerful scripting language for client-side programming,
widely used for web applications. Security concerns include cross-site
scripting (XSS) vulnerabilities.
• WebAssembly (Wasm): A binary instruction format designed for high-
performance web applications. It is sandboxed and follows the same
security policies as regular web code.
• WebViews: Enable the embedding of web content in mobile apps, allowing
interactions between web and app content. This raises security concerns,
including app-to-web and web-to-app attacks.
III. Application Stores
• Definition: Centralized platforms for distributing software, such as
Apple’s App Store and Google Play.
• Security Role: Application stores examine apps for security before
distribution, using static and dynamic analysis to prevent malicious
software and vulnerabilities.
• Security Features: Require developers to sign apps using certificates,
reducing the risk of unauthorized updates or malware. On iOS,
unsigned apps cannot be installed.
Sandboxing
1. Overview of Sandboxing
2. Application Isolation
3. Content Isolation
4. Content Security Policy (CSP)
1. Overview of Sandboxing
• Definition: Sandboxing refers to the technique used by modern
mobile and browser platforms to isolate applications and websites
from each other, enhancing security.
• Purpose: It helps protect the platform from malicious applications and
websites by restricting their interactions with each other and the
system.
Sandboxing can be
•Application Isolation
•Content Isolation
2. Application Isolation
• Mechanism: Each application runs in its own sandbox, operating
within a dedicated process with its own file system storage.
• Security Enforcement: In mobile platforms like Android, sandboxing
is set up at the kernel level, using user and group IDs, as well as
security contexts.
• Access Control: Applications are prevented from accessing each
other’s resources, with inter-app communication only allowed
through controlled interfaces.
3. Content Isolation
1. Same-Origin Policy (SOP): In web browsers, SOP isolates documents
based on their origin to prevent different documents (or websites)
from interfering with each other.
• Key Principle: Only documents from the exact same origin (matching host,
protocol, DNS name, and port number) are allowed to interact with each
other.
• Limitations of SOP: It relies on DNS instead of IP addresses, meaning
attackers who can alter DNS entries might bypass the policy.
2. Process-Based Isolation: Modern browsers run websites in separate
processes within a sandbox, adding an extra layer of security to
prevent attacks like cross-site scripting (XSS -code injection attack) and
cookie theft.
4. Content Security Policy (CSP)
• Objective: CSP provides an additional defense mechanism,
particularly against code injection attacks such as XSS.
• Functionality: Developers can use CSP to limit the sources from
which content, scripts, and media can be loaded, thereby restricting
the execution of malicious code.
• Implementation: CSP is implemented via HTTP response headers or
HTML meta tags.
Client-Side Vulnerabilities and
Mitigations
This section covers attacks and their countermeasures with a focus on
the client.
1. Phishing and Clickjacking
2. Client-Side Storage Vulnerabilities
3. Outdated Third-Party Libraries
1. Phishing and Clickjacking
Phishing and clickjacking rely on issues humans have with properly
verifying URLs and the dynamic content of rendered HTML
documents.
Here we discuss about the following:
I. Phishing
II. Clickjacking
III. Mobile Phishing & Clickjacking
I. Phishing:
• The practice of sending fraudulent communications that appear
to come from a legitimate and reputable source, usually through
email and text messaging.
• A common fraudulent attack where attackers steal sensitive
information such as login credentials and credit card numbers.
• Attackers disguise themselves as trustworthy entities (via email,
websites, SMS, etc.).
Techniques include:
• Address bar manipulation via JavaScript to show fake URLs.
• Forged websites resembling legitimate ones (e.g., misspelled URLs or
homograph attacks).
Example Attack:
A URL like https://paymentorganization.secure.server.com may
appear authentic but actually redirects to secure.server.com.
How the trick works:
"paymentorganization.secure" is just a subdomain. It can make the URL
look like it's from "paymentorganization", but it’s really a part of
"server.com".
This is a phishing trick to make the URL look trustworthy, but in reality,
it's controlled by the attacker.
1. Homograph attacks:
A homograph attack is a type of phishing attack where an attacker
tricks you into visiting a fake website by using characters in the
website address (URL) that look very similar to real ones but are
actually different. involve characters that are hard to distinguish (e.g.,
Latin "a" vs. Cyrillic "а")
Example:
A real URL: https://paypal.com
A fake URL (using a Cyrillic letter instead of a Latin letter):
https://pаypal.com
To the human eye, these look almost identical, but the second URL
leads to a fake website, designed to steal your information.
How to protect yourself:
1. User mobility: The ability for a user to access services and information while moving
across different locations or networks.
2. Device mobility: The capability of a device to move across networks without losing
connectivity or requiring reconnection.
3. Session mobility: The ability to maintain an ongoing session (e.g., a video call or
streaming) seamlessly while switching between devices or networks.
4. Service mobility (code mobility): The ability for services or applications to move across
different environments or devices, adapting to different platforms or networks.
popular types of attacks against
3G mobile networks
1. Denial of Service (DoS) Attacks
DoS attacks target the network's resources to render them unavailable to legitimate users.
Overloading the core network: Attacks flood the network with signaling messages (like
authentication requests), overwhelming its ability to process them.
Exhausting bandwidth: Excessive data usage prevents other users from accessing the
network.
4. Downgrade Attacks
SMS-based attacks involve spoofing SMS messages (impersonating a legitimate sender) or intercepting
SMS traffic. This is particularly dangerous for users relying on SMS for two-factor authentication
(2FA).
Example: An attacker sends a fake SMS from a banking service to trick users into sharing sensitive
information.
6. Authentication Attacks
3G networks use mutual authentication between the device and network, but vulnerabilities in the
authentication protocol can be exploited:
Exploiting weak encryption algorithms: Breaking the encryption used during authentication (e.g.,
A5/1 used in older GSM).
Cabir Worm: This was the first mobile phone worm. It infects Symbian
OS phones and spreads by scanning for other nearby devices
through Bluetooth. When it finds a vulnerable device, it sends a copy of
itself to infect that device. The dangerous part is that the source code
for this worm is available online, making it easier for others to create
•Mosquito Trojan: This malware affects Series 60 smartphones
(early smartphones using Symbian OS). It disguises itself as a
cracked (illegally modified) version of the "Mosquitos" mobile
phone game, tricking people into downloading it.
• These are new trends in cybercrime that are coming up with mobile computing – mobile
commerce (M- Commerce) and mobile banking (M-Banking).
• Credit card frauds are becoming commonplace given the ever-increasing power and the
ever-reducing prices of mobile hand-held devices. These factors result in the easy availability
of these gadgets to almost anyone.
• Mobile credit card transactions are now very common; new technologies combine low-cost
mobile phone technologies with the capabilities of a point-of-sale (POS) terminal.
• Today belongs to “mobile computing,” that is, anywhere anytime computing.
• The developments in wireless technology have fuelled this new mode of working for white-collar
workers.
• Wireless credit card processing is a very desirable system, because it allows businesses to
process transactions from mobile locations quickly, efficiently and professionally.
Figure 3.4 shows the basic flow of transactions involved in
purchases done using credit cards.
• Credit card companies, normally, do a good job of helping
consumers resolve identity (ID) theft problems once they
occur.
• But they could reduce ID fraud even more if they give
consumers better tools to monitor their accounts and limit
high-risk transactions
the basic flow is as follows:
1. Merchant sends a transaction to bank;
2. The bank transmits the request to the authorized cardholder [not
short message service (SMS)];
3. The cardholder approves or rejects (password protected);
4. The bank/merchant is notified;
5. The credit card transaction is completed.
Tips to Prevent Credit Card Frauds
Do’s
1. Put your signature on the card immediately upon its receipt.
2. Make the photocopy of both the sides of your card and preserve it at a safe
place to remember the card number, expiration date in case of loss of card.
3. Change the default personal identification number (PIN) received from the
bank before doing any transaction.
4. Always carry the details about contact numbers of your bank in case of loss
of your card.
5. Carry your cards in a separate pouch/card holder than your wallet.
6. Keep an eye on your card during the transaction, and ensure to get it back
immediately.
Cont..
7. Preserve all the receipts to compare with credit card invoice.
8. Reconcile your monthly invoice/statement with your receipts.
9. Report immediately any discrepancy observed in the monthly
invoice/statement.
10. Destroy all the receipts after reconciling it with the monthly invoice/statement.
11. Inform your bank in advance, about any change in your contact details such as
home address, cell phone number and E-Mail address.
12. Ensure the legitimacy of the website before providing any of your card details.
13. Report the loss of the card immediately in your bank and at the police station, if
necessary.
Dont’s
1. Store your card number and PINs in your cell.
2. Lend your cards to anyone.
3. Leave cards or transaction receipts lying around.
4. Sign a blank receipt (if the transaction details are not legible, ask for another
receipt to ensure the amount instead of trusting the seller).
5. Write your card number/PIN on a postcard or the outside of an envelope.
6. Give out immediately your account number over the phone (unless you are
calling to a company/ to your bank).
7. Destroy credit card receipts by simply dropping into garbage box/dustbin
Types and Techniques of Credit Card Frauds:
• Traditional Techniques:
• Application fraud
• Illegal use of lost and stolen cards
1. Application fraud
The traditional and the first type of credit card fraud is paper-based fraud – application fraud,
wherein a criminal uses stolen or fake documents such as utility bills and bank statements
that can build up useful personally Identifiable Information (PII) to open an account in
someone else’s name.
Application fraud can be divided into:
1. ID theft: Where an individual pretends to be someone else
2. Financial fraud: Where an individual gives false information about his or her
financial status to acquire credit.
2. Illegal use of lost and stolen cards is another form of traditional technique. Stealing a
credit card is either by pickpocket or from postal service before it reaches its final
• Modern Techniques
1. Skimming is where the information held on either the
magnetic strip on the back of the credit card or the data
stored on the smart chip is copied from one card to another.
2. Site cloning and false merchant sites on the Internet are
becoming a popular method of fraud and to direct the users
to such bogus/fake sites is called Phishing. Such sites are
designed to get people to hand over their credit card details
without realizing that they have been directed to a fake
weblink /website (i.e., they have been scammed).
Cont..
3. Triangulation: It is another method of credit card fraud and works in the
fashion as explained further.
1. The criminal creates a fake website that looks like a real store and
offers products at super low prices to attract people.
2. A customer visits the fake website, registers with their personal
information (name, address, etc.), and provides their credit card
details to buy the product.
3. The criminal doesn’t use the customer’s credit card directly.
4. Instead, they use stolen credit card details from someone else
to buy the same product from a legitimate website and ship it to
the customer’s address.
5. The customer receives the product, so they think everything is fine.
6. Meanwhile, the criminal keeps using stolen credit card details to
make more purchases for other customers and eventually shuts
down the fake website to avoid getting caught.
7. Then, they start the whole process again with a new fake site.
Cont..
• The criminal gains by making money from selling products
that are paid for using someone else's stolen credit card,
while also reducing the risk of getting caught because they never
physically handle the stolen goods themselves.
Organizations need to be aware of these risks to set up proper security rules. As more people
use mobile devices, two types of challenges arise:
• Microchallenges: These are challenges on the individual device level, such as how to protect
data on each phone or tablet.
• Macrochallenges: These affect the entire organization, like how to manage security when
many employees are using mobile devices.
Some well-known technical issues in mobile security include things like managing device settings,
ensuring secure login methods, protecting data through encryption, securing network
connections, and controlling media players and apps on mobile devices.
5. REGISTRY SETTINGS FOR
MOBILE DEVICES
Registry settings for mobile devices are like a set of instructions or
rules that tell the device how to behave. These settings control
important functions, such as:
1.What apps can be installed or run on the device?
2.How the device connects to the internet or other networks.
3.How security features like passwords, encryption, or firewalls
should work.
4.System preferences, like whether updates are automatically
installed or how notifications are handled.
The issue of registry settings on mobile devices with an example:
• Microsoft ActiveSync is a tool that helps users synchronize (or
transfer) data between their Windows-powered PCs and Windows
mobile devices.
• This includes things like emails, calendar events, notes, contacts, and
even files like pictures, music, and documents.
• Imagine you use ActiveSync to make sure that everything on your PC
is also available on your mobile device, so you can access your
emails, calendar, and files on the go.
• ActiveSync can also sync directly with the Microsoft Exchange server,
allowing your emails, contacts, and calendar to stay up-to-date
wirelessly even when you are far from your PC.
• Registry setting becomes an important issue given
the ease with which various applications allow a
free flow of information
• Mobile devices and computers face security risks from things like
Spyware, viruses, worms, malware, and other harmful programs that can
spread through networks and the internet.
• To fight these, there are new mobile apps being developed all the time to
protect against these threats.
• One problem with Windows devices (both computers and mobile devices)
is that when you first set them up, they might not be fully secure.
• Even if you go through all the settings in the Control Panel or other
menus, the security might still not be strong enough.
• For example, some important security settings can only be changed by
modifying the registry.
• The registry is like a hidden control center for how the device operates,
and certain security improvements can only be made by changing these
settings, which are not always visible in regular menus.
6. AUTHENTICATION SERVICE SECURITY
• There are two components of security in mobile computing: security of devices and
security in networks.
• A secure network access involves mutual authentication between the device and the base
stations or Web servers.
• This is to ensure that only authenticated devices can be connected to the network for
obtaining the requested services.
• No Malicious Code can impersonate (imitate) the service provider to trick the device into
doing something it does not mean to. Thus, the networks also play a crucial role in security
of mobile devices.
• Some eminent kinds of attacks to which mobile devices are subjected to are: push attacks,
pull attacks and crash attacks
• Authentication services security is important given the typical attacks on mobile devices
through wireless networks: DoS attacks, traffic analysis, eavesdropping, man-in-the
middle attacks and session hijacking.
AUTHENTICATION SERVICE SECURITY
VICE SECURITY
65
1. Cryptographic Security for Mobile Devices
67
Cont..
• CGA in Mobile and Handheld Devices
• Used in Context-Aware Mobile Computing: Secures
communications in mobile applications based on context and
location.
• Palm Devices: These are common handheld devices (like PDAs) in
mobile computing that can take advantage of cryptographic
security features.
• Cryptographic Security on Palm Devices is provided by
Cryptographic Provider Manager (CPM) in Palm OS-5:
Provides systemwide encryption services.
Allows applications to encrypt selected data or all data on
the device for security.
AUTHENTICATION SERVICE SECURITY
2. LDAP (Lightweight Directory Access Protocol) Security for
Hand-Held Mobile Computing Devices
73
AUTHENTICATION SERVICE SECURITY
5. Networking API Security for Mobile Computing Applications
• With the advent of electronic commerce (E-Commerce) and its further off-shoot into
MCommerce, online payments are becoming a common phenomenon with the payment
gateways accessed remotely and possibly wirelessly.
• Furthermore, with the advent of Web services and their use in mobile computing applications,
the API has become an important consideration.
• Already, there are organizations announcing the development of various APIs to enable software
and hardware developers to write single applications
• Most of these developments are targeted specifically at securing a range of embedded and
consumer products, including those running OSs such as Linux, Symbian, Microsoft Windows CE
and Microsoft Windows Mobile (the last three are the most commonly used OSs for mobile
devices).
• Technological developments such as these provide the ability to significantly improve
cybersecurity of a wide range of consumer as well as mobile devices. Providing a common
software framework, APIs will become an important enabler of new and higher value services.
74
ATTACKS ON MOBILE/CELL
PHONES
Task-4 : write in your note book about the
following attacks on mobile phones, how they are
performed (tools), and tips to secure from these
attacks:
•Mobile Phone Theft
•Mobile Viruses
•Mishing -> Mobile Phishing
•Vishing-> social engineering over the
telephone
•Smishing -> SMS PhISHING
•Hacking Bluetooth
ATTACKS ON MOBILE/CELL PHONES
Mobile Phone Theft
• Mobile phones have become an integral part of everbody’s life and the mobile phone
has transformed from being a luxury to a bare necessity.
• Theft of mobile phones has risen dramatically over the past few years.
• Since huge section of working population in India use public transport, major locations
where theft occurs are bus stops, railway stations and traffic signals.
• Many Insurance Companies have stopped offering Mobile Theft Insurance due to a large
number of false claims.
• When anyone looses his/her mobile phone, more than anything “Contact List” and
“Personally Identifiable Information (PII)”, that really matter, are lost
• One might have just thought that his/her cell phone is much safer than a PC that is very
often attacked by viruses; however, criminals made this thought as false statement.