INFORMATION SYSTEMS FOR MANAGERS

CASE ANALYSIS
FINTECH: CHOOSING A CLOUD SERVICES
PROVIDER
Submitted By:
Section – C
Group – 8
•ARNAB KUMAR DAS (2017PGP069)
•DINESH KUMAR YADAV (2017PGP111)
•DISHARI BANERJEE (2017PGP113)
•JANANI S (2017PGP144)
•KARTHEEPAN K (2017PGP164)
•REUEL DANIEL LUNGLENG (2017PGP297)
•SANJNA SANJIV (2014IPM079)
HOW WOULD A MOVE TO THE CLOUD MAKE IT EASIER AND/OR MORE
PROFITABLE FOR FINTECH TO PROVIDE LARGE VOLUMES OF SELECTED DATA TO
ITS CLIENTS?

Fintech could rent a cloud service instead of

making heavy up-front investments in
computers and software.
 Cloud computing also transferred the work
associated with updating infrastructure and
ensuring high reliability to providers who were
able to capitalize on their extensive experience
and scale.
WHAT TECHNICAL CHALLENGES DOES FINTECH FACE IN
OFFERING THE NEW SERVICE?
Security Concerns in the Cloud:
 Data breaches
 Compromised credentials and broken authentication
 Hacked interfaces and APIs
 Exploited system vulnerabilities
 Account hijacking
 Malicious insiders
 The APT (Advanced Persistent Threats) “parasite”
 Permanent data loss
 Inadequate diligence
 Cloud service abuses
 DoS (Denial of Service) attacks
 Shared technology, shared dangers
WHAT BUSINESS CHALLENGES DOES FINTECH FACE IN
OFFERING THE NEW SERVICE?

 Cost
 Reliability

 Regulation
ASSUME JOE KWO MUST CHOOSE A CLOUD SERVICES PROVIDER. BASED ONLY ON INFORMATION PROVIDED IN THE
CASE, WHICH PROVIDER SHOULD KWO CHOOSE? WHY? YOU WILL NEED TO COMPARE AND CONTRAST THE THREE
PROVIDERS’ OFFERINGS IN DETAIL, AND PREPARE TO DISCUSS TECHNICAL AND BUSINESS IMPLICATIONS OF THEIR
SIMILARITIES AND DIFFERENCES.

Criteria Better Provider

Training AWS, Google
 Based on the evaluation
System AWS, Azure criteria, we feel that
Administration
Support Amazon Web Services
Customer AWS provides the ideal
Support
Data and AWS, Azure features that Fintech
System
Availability
requires.
Security AWS, Google
Programmabilit AWS, Azure
y
Cost AWS
FOR EACH PROVIDER (AMAZON, GOOGLE, MICROSOFT), IDENTIFY SPECIFIC RISKS,
AND PREPARE TO OFFER SPECIFIC SUGGESTIONS FOR LAUNCHING, RUNNING,
AND MANAGING THE PROPOSED NEW SERVICE IF THAT PROVIDER IS CHOSEN.

RISKS
Amazon Web Service Google Cloud Platform Microsoft Azure

•lack of understanding •Upfront costs were not •Potential loss of account

where security clear control to Microsoft.
responsibilities begin and •Unsure about Data •Increased competition for
end with the provider Warehouse development resources.
•lack of security •SDK was Google cloud •Shift to volume business.
configuration within the specific •Decline in upfront profit
areas that an AWS •Termination fees were not and revenue collection.
consumer is responsible to shared •Accelerated globalization
manage and market competition.
•Compliance issues •Increased self-hosting and
•Many data breaches come integration costs.
through accounts that
should have been deleted
or deactivated long before
the breach instance.
ANS.3 (CONTD...)
STEPS
Launching Running Managing
•A common •Skilled technical •Scalability in
database should employees and terms of storage,
be used with consultants uptime and RA
common •Good customer •Maintenance
attributes to support •Updated Security
resolve data •Resources Measures
integration locally available
problems
•Testing
EVALUATE STRENGTHS AND WEAKNESSES OF THE PROVIDER EVALUATION PROCE
SS DESCRIBED IN THE CASE. WHAT USEFUL STEPS WERE TAKEN? DO YOU SEE
ANY PROBLEMS?

WEAKNESS –
Other than Nolte,
STRENGTH - Well no one from
Defined Use Case Fintech involved in
the evaluation
process

USEFUL STEP
PROBLEM – Kwo
TAKEN – Various
was suspicious
technical &
about meeting
economic factors
clients’
were taken into
expectations
consideration