DEVELOPMENT OF SECURE CLOUD TRANSMISSION PROTOCOL (SCTP) ENGINEERING PHASES : MULTILEVEL SECURITY & CRYPTOGRAPHY

International Journal on Cryptography and Information Security (IJCIS), Vol. 5, No. 3/4, December 2015
DOI:10.5121/ijcis.2015.5404 33
DEVELOPMENT OF SECURE CLOUD
TRANSMISSION PROTOCOL (SCTP)
ENGINEERING PHASES : MULTILEVEL
SECURITY & CRYPTOGRAPHY
Dinesha H A1
and Dr.Vinod K Agrawal2
1
PhD Student , Dept of ISE, PESIT. Bangalore , India
2
Professor , Dept of iSE, PESIT Bangalore, India
ABSTRACT
Cloud computing technology provides various internet-based services. Many cloud computing vendors are
offering cloud services through their own service mechanism. These mechanisms consist of various service
parameters such as authentication, security, performance, availability, etc. Customer can access these
cloud services through web browsers using http protocols. Each protocol has its own way of achieving the
request-response services, authentication, confidentiality and etc. Cloud computing is an internet-based
technology, which provides Infrastructure, Storage, Platform services on demand through a browser using
HTTP protocols. These protocol features can be enhanced using cloud specific protocol, which provides
strong authentication, confidentiality, security, integrity, availability and accessibility. We are proposing
and presenting the secure cloud transmission protocol (SCTP) engineering phases which sits on top of
existing http protocols to provide strong authentication security and confidentiality using multi-models.
SCTP has multi-level and multi-dimensional approach to achieve strong authentication and multi-level
security technique to achieve secure channel. This protocol can add on to existing http protocols. It can be
used in any cloud services. This paper presents proposed Protocol engineering phases such as Service
Specification, Synthesis, Analysis, Modelling, and Implementation model with test suites. This paper is
represents complete integration of our earlier proposed and published multilevel techniques.
KEYWORDS:
Authentication, Confidentiality, Multi-dimensional, Multi-level, Security, SCTP;
1. INTRODUCTION
A protocol is a set of rules which governs in between two communication ports. Protocol
engineering describes as an application of formal methods and software engineering in the
development of communication protocol. TCP/IP, UDP and HTTP are the major existing
communication protocols used in between communication parties. Many internet communication
and web services are possible with the internet protocol. Cloud computing is an internet service
which provides on demand platforms, storage, infrastructure and related services. It has been
facing many security issues as reported in literature [1-10]. Poor identity and access management
procedures, implementation of poor access control, procedures create many threat opportunities.
Cloud authorization and Authentication issues are reported by TCS Innovation Labs and many

34
more organizations [1]. HP Labs in 2011 reported demerits on the lack of user control,
unauthorized secondary usage, access, audit and lack of customer trust [2]. Accenture lab in 2011,
reported concerns around cloud access authentication, authorization and access control,
encrypted data communication, multi-device access, multi-level authentications and user identity
management [3]. CA technologies in 2013 raised issues pertaining to identification and
authentication of users’ survey calculation before granting access to cloud information or
infrastructure [4]. Nelson Gonzalez1*, Charles Miers1,4, Fernando Red´ıgolo1, Marcos
Simpl´ıcio1, Tereza Carvalho1, Mats N¨aslund2 and Makan Pourzandi3[5], mentioned regarding
identity and access management, enabling authentication for cloud solutions while maintaining
security levels and availability for customers and organizations. They mentioned the user access,
authentication and privacy as novel concerns [5].
Cloud computing can be improved by specialized security design and security protocol, which
works with existing protocol and activates during cloud transaction to ensure strong
authentication, security and confidentiality. Many cloud authentication protocols were proposed
and used to avoid authentication issues. Kerberos protocol is fruitless with one flaw of replay
attack. The Open ID authentication protocol is luckless in phishing vulnerabilities [6]. O Auth
Protocol reports Kerberos on several aspects and thus has comparable advantages and drawbacks
[6][7]. All these protocols rely on user’s memorable passwords [6]. A zero knowledge
authentication protocol and Sedici 2.0 protocol is used in third party authentication, but it
depends on passwords and authentication [6]. Many cloud protocols have been introduced such as
Gossip protocol [7], Dynamic auditing protocol [8], Access protocol [9], Cloud Fault Tolerance
Protocol [10], Cloud Gossip Protocol for Dynamic Resource Management Agent-Based User
Authentication [11] and Access Control-2013 [12-14]. Many cloud authentication schemes are
proposed in literature such as Graphic Password Authentication [15], Biometric Authentication
[16], Secured Biometric Authentication [16,17], RFID- based authentication [18] and Eid
Authentication [19,20] with their own limitations. Literature study about cloud authentication
issues, security importance, proposed solution demerits motivate us to take an objective of cloud
strong authentication and secure channel to achieve customer trust, privacy, confidentiality and
satisfaction. In this paper, we propose to secure cloud transmission protocol, which works with
existing internet protocols to ensure strong authentication, privacy, customer trust,security and
confidentiality.
Proposed secure cloud transmission protocol (SCTP) has its own communication technique,
technology, algorithms to achieve strong authentication, security and confidentiality [21]. SCTP
may be a solution to the issues reported in literature, such as i) Authenticated Access based on
user types (privileged access rights) ii) Data protection and Integrity iii) Poor identity and access
management procedures,and Implementation of poor access control and procedures. Proposed
SCTP has multi-dimensional password generation and authentication system [22], Multilevel
Authentication technique [23] and Multi-level Cryptography system with Metadata and Lock
Approach for Storing Data in Cloud [24]. This protocol can be further improved with cloud
usage profile- based intruder detection system [25].
Figure 1 presents SCTP phases from requirements specification to Implementation. Different
Phases are: i) SCTP requirements specifications to ensure strong authentication and secure
channel ii) SCTP Service synthesis to make the error- free protocol specification and to
combine multiple protocol specifications into an error- free protocol specification. iii) SCTP
Modelling and specifications to present the exchange sequences, multi-level authentication,

35
multi-dimensional password, multi-level Cryptography and Finite state machine modelling. iv)
SCTP implementation to take the SCTP specification and develop SCTP software modules. v)
SCTP verification to verify if the SCTP specification actually realizes the SCTP service
specification or not vi) SCTP Validation to check that SCTP specification does not get into
deadlock, unspecified reception, and live lock errors. vii) Conformance testing to test the given
a SCTP specification, generate test-suite for proving complete testing the SCTP functionalities.
Figure 1: SCTP phases
This paper is an integration of earlier proposed and published multilevel authentication,
multidimensional password generation and multilevel cryptography techniques. It is organized in
the following manner: Chapter 2, presents the SCT protocol requirement specification, Chapter 3,
presents SCT protocol synthesis and modelling, Chapter 4 , presents SCT protocol analysis,
Chapter 5, presents SCT protocol implementation modules, Chapter 6, presents SCT protocol
conformance testing. Chapter 7 concludes the paper along with future enhancement.
2. SCT PROTOCOL REQUIREMENT SPECIFICATION AND
SYNTHESIS
This section describes the SCTP requirements specification in cloud computing. Given below are
the two major specifications:

36
Requirement Specification 1: Strong Authentication
Cloud computing provides on demand storage, infrastructure (Virtual Machines), platforms
(development space) services to customers. The customer may use these services in storing their
confidential data, developing important product codes, designing important software, creating
software environment, testing their products/software, writing research reports and others manual,
etc. Hence, each operation of customers can be considered as confidential. The vendor must make
necessary arrangement in restricting the user operation based on their privileges. It shall not be
accessed and breached by unauthenticated user within and outside the organization. Hence,
authentication and authorization are important service specifications in cloud computing. These
services and operations are only accessible to authenticated organization for its authorized users.
Two important security aspects here are: i) Organization/customer must be authenticated. ii)
Particular user must be authorized to perform the particular operation.
Requirement Specification 2: Secure Channel
The secure channel is an important requirement. Customer data must send or upload in secured
channel. It is possible with cryptographic technique. Customer data must release from the
customer place in a cipher text form. Cloud storage service acts as a container for cipher texts.
The vendor provides only storages to the customer. The vendor may use much better
cryptographic algorithms to store customer data in encrypted form. Though vendor has many
techniques/Service Level Agreements, it is difficult to make customer understand and earn
customer trust and satisfaction. Hence, we recommend customer side encryption to achieve the
secure channel and trust.
We can conclude secure cloud transmission protocol with two important service specifications,
they are: i) Strong Authentication ii) Secure Channel
Figure 2 shows the SCTP service specification in cloud computing services wherein it shows the
major specification described above, along with the different attack scenarios. The requirements
specification is presented in such a way that i) Inside attacker or Unauthorized accesses are to be
restricted, ii) Outside attacker must not be able to break the confidentiality and security iii) Cloud
services must be accessed by authorized customer and specific operation must permit only
authenticate privileged user iv) Data uploading must take place with the only authenticated user
in secure cipher form over secure channel.

37
Figure 2 SCTP service specification
SCTP string authentication executes while accessing the cloud service. SCTP secure channel
executes while uploading the data to the cloud. Both are independent and can happen parallel.
Hence,the error free protocol specification can be combined in SCTP service specification 1 & 2.
3. SCT PROTOCOL SYNTHESIS AND MODELING
This section describes the SCT protocol synthesis and FSM modelling.
SCT Protocol Synthesis
As described in section 2, Strong authentication and secure channel are the two main requirement
specifications of SCTP. These objectives can be achieved using multi- model structure. Strong
authentication can be achieved using the multi-dimensional password system and multi-level
authentication (MLA) technique which are described in [22] and [23]. Secure channel can be
achieved using multi-level cryptography with Metadata and Lock approach for storing data in the
cloud which is described in [24]. Hence, protocol specification can be derived as i) Multi-level-
Multi-dimensional password (MDP) Authentication and ii) Multi-level cryptography (MLC).
While customer is accessing cloud services like PaaS, IaaS, SaaS and related [26], SCTP must
execute multi-level and multi-dimensional approach. When customer initiates SaaS and related
operations, SCTP must execute multi-level cryptography approach to create secure channel.

38
SCT Protocol Modelling
Figure 3 shows the finite state machine (FSM) modelling of SCTP.
Figure 4: FSM-SCTP
Figure 3(a)(b) shows the finite state machine for SCTP, finite states derived for both objectives.
Fig 3 (a) shows the authorization and authentication finite state model using multilevel and
multi- dimensional password system. It clearly mentions service usage as final/finite stage and the
attacker is trap state, and remaining as a transition stage. Fig 3(b) shows the secure channel finite
state model using multi-level cryptography.Send/Upload is marked as a final/finite state, stop is
marked as a trap state. Remaining states refer to transition state which indicates the MLC process.
Table 1 represents the state transition table for FSM-SCTP (a) where it shows cloud usage final
state feasible with only valid transition. Table 2, represents the state transition table for FSM-
SCTP (b) which presents secure channel state transition. Algorithm 1
SCTP_STRONG_AUTHENTICATION presents the steps to create strong authentication.
Algorithm 2 SCTP_SECURE _CHANNEL represents steps to achieve the secure channel.

39
Table 1 state transition table for FSM-SCTP (a)
Current State Input Next State
Generate MDP S Check MDP For
authentication
Authenticate MDP S Enter into MLA
1st
Level Authenticate S Enter Second Level
2nd
Level Authenticate S Enter Nth Level
Nth Level
Authenticate
s Allow for cloud
usage
Any above state Fail Consider as
attacker/misbehave
Table 2 state transition table for FSM-SCTP (b)
Current State Input Next State
Metadata Yes Cryptography
Cryptography Yes Lock
Lock Yes Send/Upload
Any above state No Stop Sending/SaaS
Algorithm 1: SCTP_STRONG_AUTHENTICATION
Input: Image1..n, Text1..n, MDPi
Output : D, SaaS, PaaS, IaaS
Step 1: Cloud connection establishment between vendor and customer over internet
CV
Step 2: Generate Multi-dimensional password system using multi- format inputs for
multiple levels
K1 MDP_Generation (Image1, Text1, Image n, Text n) /*To detect outside
attacker*/
K2 MDP_Generation (Image1, Text1, Image n, Text n) /*To detect inside
attacker*/
KnMDP_Generation (Image1, Text1, Image n, Text n) /*To ensure access
privileges and grant access*/
MDP_Generation (Image1, Text1, Imagen, Textn)
{
//Arithmetic/Logic Operation for input Images
If (Imges number > 1) then
Img_Opn= Airthmatic_Logic(Image1,Image2..Imagen)
//Extract Features of final image after arithmetic or logic operation i.e Img_Opn
ImageFeature= Extract Features (Img_Opn)

40
// Combine all text inputs in random way
If(texts_number>1) then
PasswordText= RandomMix(Text1,Tex2,..Textn)
// Combine final text and final features of image
MDP=Combined _File (ImageFeature, PasswordText)
Return MDP
}
Step 3: Allow to enter MDP input, Check entered MDP input against Generated MDP
data base i.e K1, K2,K3..Kn
Initialize j1
Repeat the below steps until j=n
MDPi Entered MDP Input
IF MDPi=Kj THEN
Then jj+1
ELSE
FlagJ
Go to Step 4
END IF
Go to Step 5
Step 4: Analyze the flag value
Switch (Flag)
case 1:
DTrigger True positive and display outside attack;
break;
case 2:
D Trigger true positive and display inside attacker;
break;
case n:
D Trigger true positive and display misused privileges;
End Switch
Try again! Go to step 3
Step 5: Allow accessing cloud services and performing intending operations.
Confirm Concatenated MDPi (1,2….n) = Concatenated (K1,K2…Kn)
Then CSaaS, PaaS, IaaS
Algorithm 2: SCTP_SECURE _CHANNEL
Input: plain data Pd
output: cipher data Cd
Step 1: Start Multilevel cryptography executes metadata, encryption and end with lock
Md Metadata (Pd)

41
Repeat below step till all encryption level completes
EdEncrypt (Md, Key)
CdLock(Ed)
Step 2: Send, upload to cloud SaaS
IF (Cd)) THEN
SaaSCd
ELSE
Goto Step 1
End
Step 3: While retrieving Cd, MLC executes Unlock, Decrypt, Reverse Metadata
EdUnlock (Cd)
Repeat below step till all decryption level completes
MdDecrypt(Ed,Key)
Pd~Metadata (Md)
Step 4: End of Multi-level cryptography
SCTP Verification & Validation
The above FSM, transition and algorithms verify and confirm the requirements specification of
strong authentication and secure channel discussed in section 2. MDP-MLA and MLC techniques
are applied, modelled in wireless sensor-cloud integration using an ant colony routing algorithm
using Petri-nets theory [27][28].
SCTP Validation against deadlock: Deadlock occurs, when processes chain waits for some
action to occur, when resources are occupied and not released and when complex and parallel
action takes place. SCTP MLA, MDP and MLC functionalities are designed to happen one after
another,no resources and inputs are shared, no parallel action takes place as it travels from level
to level, hence there will be no deadlock. This issue has been taken care of. The unspecified
reception isn’t happening due to protocol design consideration for internal fixed levels and inputs
from a specific limited user. The unspecified reception issue is incorporated.
SCTP Validation against live lock: Livelock is a special case of resource starvation. In SCTP,
we can correlate livelock resource starvation for MDP input/process, MLA movement and
MLC data/process. MDP-MLA occurs in sequence from level to level. No parallel level executes
at a time. MLC designed in an independent way in sequence, hence livelock issue may not occur.
4. SCT PROTOCOL ANALYSIS
This section analyzes the SCTP protocol MDP password strength for MLA authentication. It
analyses secure channel and its performance by creating attacker, unauthorized user scenarios.

42
Applying set theory for analyzing MDP in MLA, let us assume 3 inputs for MDP generation and
3 levels like L1, L2 and L3 for authentication. MDP generation takes both images (img1, img2,..
Imgn) and texts (text1, text2 ..textn) passwords. The universal sets U = ( img1, img2, img3,
img4, img5, text1,text2,text3,text4} can be declared to handle 3 MDP in 3 MLA. The
corresponding sub sets for eack level are derived below:
L1= {img1, img2, text1}
L2= {img3, text2, text3}
L3= {img4, img5, text4}
Then, the venn diagram is as in figure 4
Figure 4: MDP_MLA Venn diagram
MLA=Concatenate (MDP (L1), MDP (L2),MDP (L3)) //Final authentication for accessing the
service.
Refer to MDP MLA venn diagram 4 figure, MDP confidential inputs for different levels are
different in nature, L1,L2 and L3 are considered as disjoint sets. ……..1
Refer to universal sets the U can be
U = L1 U L2 U L3 & Null = L1 ∩ L2 ∩ L3
Then
Number of sample space (total confidential data) can be defined as number of onfidential inputs
at each individual levels L1, L2 and L3 as defined below:
n(s) = n(L1 U L2 U L3)=n (L1) + n(L2) +n(L3)
Number of confidential data required to break the system is n(s).
We used probability theory to analyze SCTP features and estimates the probability of breaking.
Probability models can greatly help system in optimizing multi- mode levels and making safe
decisions to have proved MLD MDP and MLC.
Since it is disjoint and algorithm, designed to not to occur simultaneously, L1, L2, L3…..Ln is
considered as a mutually exclusive event.
AI, A2, • • • , An is a finite sequence of mutually exclusive events in S (A; n Aj = 0 for i'#: j),
then probability to break the system ‘p’ can be derived as below:
L1 L2 L3

43
,
Probability to break each level is P(Ai), levels may go up to ‘∞’. ‘p’ can be probability of
breaking the complete system.
Now, to analyze the probability to get successful three inputs to break each level using brute force
or dictionary attack which contain ‘n’ guessed inputs. Analyze the probability to get successful
n(L1UL1UL3) in a guessed ‘m’ dictionary or brute force lists. The derivation after applying the
law of probability formula for MLA_MDP. Probability of breaking event E can be defined as
probability of levels P(L1), P(L2)… P(Ln) breaking .
P(E)=P(L1)P(E/L1) + P(L2)P(E/L2)+ P(L3)P(E/L3)….. P(Ln)P(E/Ln)
Probability of breaking each level with ‘n’ confidentiality input breaks is referred as p(Ak/E). It
can be defined using Bayes theorem as below:
for n=1,2,3..n levels,
P(An|E)= P(An)P(E|An)
----------------------
P(E)
 P(An)P(E|An)
----------------------------------------------
P(L1)P(E/L1) + P(L2)P(E/L2)+ P(L3)P(E/L3)…P(Ln)P(E/Ln)
Above Bayes theorem expression proves that probability of breaking proposed MLA system i.e
P(An/E) depends on the attacker success on each levels, i.e L1, L2, .. Ln i.e on P(L1)P(E/L1) ,
P(L2)P(E/L2), P(L3)P(E/L3)…P(Ln)P(E/Ln) events. Hence, it proves the criticality of breaking
confidential inputs.
Analyzing the Strength of Multi-dimensional Password
The National Institute of Standards and Technology (NIST) password meter tries to estimate the
entropy of a password mainly based on their length. A password strength meter is a function i.e
f=  R, that takes as input a string (or password) x over an alphabets ∑ and outputs a number
s, a score, which is a measure of the strength of string x as a password. The output is, in general, a
real number indicating the password strength.
Consider currently using normal textual password length L, from a set of N possible symbols.
The number of possible passwords can be found by increasing the number of symbols to the
power L, i.e. NL
. Increasing either L or N will strengthen password. The strength of a random
password can be measured by the information entropy is just the base-2 logarithm or log2 of the
number of possible passwords. Assuming each symbol in the password is produced
independently, a random password's information entropy, H, is given by the formula as below:
Where, N is the number of possible symbols, L is the number of symbols in the password. H is
measured in bits. In MDP inputs such as images, texts and operations gives increased N and L
which results in increased strength compared to textual passwords.

44
The strength of a password is the amount of work an adversary needs to break the password.
Consequently, the optimal strategy for an attacker is to guess passwords in increasing order of
strength and decreasing order of probability, i.e., more likely passwords are tried before less
likely ones. This also motivates the definition of guessing entropy, which gives the average
number of passwords an attacker has to guess before finding the correct one. Let X be a random
variable with finite domain D and P(X = di) = pi, ordered with decreasing probabilities pi < pj for
i < j. The guessing entropy G(X) is defined as Equation 1 = G(X)
An Ideal Password Strength Meter Definition 1
Let us fix probabilities P:∑* [0 1] on the space of passwords (i.e., strings over a certain
alphabet). An ideal password checker f(x) is given by the function f(x) = -log(P(x)). We denote
this password strength meter as “ideal”, as the order which is given by this function is the same as
the order with which passwords are guessed in an optimal guessing attack. Consequently, the
following two functions f’(x) = 1=P(x) and f’’(x) = RP (x) also constitute ideal password
checkers, where RP (x) is the rank of x according to the distribution P, i.e., if the probabilities pi
= P(xi) are ordered with pi < pj for i < j, then RP (xi) = i.
An adaptive password strength meter (APSM) proposed in [29] f (x, L) is a function f:∑*(x∑*)k
 R, that takes a string (or password) x over an alphabet ∑ and a password file L containing a
number of passwords as input and outputs a score S. Password database L contains a number of
Passwords sampled from the same distribution, and the task of the password strength meter is to
estimate the strength of the password x based on his estimation of P [29].
Over the last years, Markov models have proved to be very useful for computer security in
general and for password security in particular. For example, Narayanan et al. [29] showed the
effectiveness of Markov models to password cracking [29].
For breaking the password:
f(c) = -log2(πmi=1 P(ci|ci-n+1,…ci-1))
MLA-MDP password generated in multi-level with combinations of special and alphanumerical
characters in more than 30 characters. The generated password in the above equation, proves
MDP strength.
Strong Authentication
The multi-dimensional password generation system uses multiple inputs to generate password
and generated password is used in authenticating the user in multiple levels. Hence, to analyze the
proposed protocol authentication and security, we used probability theory. Below section presents
the (a) probability of breaking the MDP-MLA authentication and getting strong authentication
and (b) probability of breaking MLC security and getting secure channel. We compare our work
to three different password checkers that are widely used today- the NIST, Google and Microsoft

45
password checkers. They were chosen because of their popularity and because they are
representative for the techniques employed currently for password strength meters.
(a). Probability of breaking the authentication
To break the MDP-MLA system one should know, all the ‘N’ confidential inputs to create MDP’s
for the all the ‘M’ levels. MDP=1,2…N MLA = 1,2,… M. Hence, the probability of breaking by
identifying N inputs in M levels is found. Probability of breaking MDP-MLA can be P (B)/P(S)
= i.e 1/2N
/M = for N=4 and M=4 the result will be => 0.015625.
Below table 3 executes the proposed authentication with different M inputs and N values.
Table 3: Authentication with different inputs and levels
Values Meaning
Formula
Result
Conclusion
N=0 M=0 No security 1 Certain to break
N=1 M=1 Single input password for only 1 level 0.5 Chance to break
N=2 M=2 Two input password for 2 levels 0.125 Difficult to break
N=3 M=3 Three input password (MDP) for 3 levels 0.0416 Unlikely to break
N=4 M=4 Four input password (MDP) for 4 levels 0.015625 Strong Authentication
Figure 4: MDP-MLA Strong authentication
Figure 4, represents the strong authentication with increased inputs and levels. MDP MLA
achieves strong authentication as the number of inputs and levels increases. Initial M=N=0 value
creates zero authentication, M=N=1 generates weak system, M=N=2 produces an average system,
M=N=3 and 4 creates a strong authentication system. MDP_MLA system is stronger than single
level authentication or 2 levels with single/double input password. It cannot be broken with
dictionary and other brute force and similar attacks.

46
EXPERIMENTATION & DISCUSSION
Case Study Example: Consider a university ‘X’ as a customer for keeping all its affiliated
college’s student’s admission, examinations, marks card and other related data. The huge
student’s information cannot be maintained in single PC or server. Cloud Storage service can be
used for best repository. It may be private or public cloud storage service. Let us take marks card
data as a sensitive data which should not modify or update by unauthenticated user. A single
password authentication, biometric, smart card, single level authentication cannot be used to
access the marks card storage as it may breach confidentiality. Confidentiality cannot be depend
on single person and privileges. So let us, introduce multi-level and multi-dimensional password
authentication system which authenticates users in multiple levels and authorizes access
privileges for university marks card storage.
MDP authentication for accessing cloud services such as Storage as a service could be the best
solution to authenticate and authorize the user. Using multiple authentication, in a first level/Top
level, Vice chancellor/University Head authenticates the cloud services, In second level
Examination, head authenticates second level for accessing the data inside the department, third
level (may be bottom level) is used to authenticate and authorize privileges to perform a
particular operation. At each Level, MDP techniques take place. Generated MDP has to be tested
in multiple levels. MDP generator uses images and texts combination. Images may be university
unique logo, Individual signature in image form, Seal etc. Text may be confidential textual inputs
like password, university name and etc.
Experiment: Assuming the number of levels is 3, multi-level and multi-dimensional
inputs are 3 in each level, image arithmetic and logic operation as add, random mix
function for texts, Consider the table below and let us do the operation.
Discussion:
Since images are defined by company individuals, Image size, RGB, Pixel and other image
factors are difficult to guess. Even if a hacker breaks for single image, they will have multiple
image challenges along with textual passwords to break. Assuming the successful hacking of all
MDP inputs, the hacker will face the challenge of breaking multiple levels. Hence, single hackers
and system cannot do this. Brute force attack and dictionary attack can identify the textual
passwords, not images, even with further improvements of attack breaking the images multilevel
break cannot be done.
Experimentation
Assuming a number of levels and number of inputs to MLA MDP is 3, Image operation is
multiplication and table below is assumed confidential data, then the concatenated password
obtained in all three levels is described below:

47
Sl No Level Assumed confidential Inputs Algorithm output
1 First X logo, VC Sign, “x@qwerty” Kjhbdd987e68e6ghjbsdkjhgj
2 Second Exam section seal, Registrar sign, “X@123” J90823020sdgj@#%^&(*&^%
d
3 Third Sign , secrete code ig, “ex@m123” #$^&(hgjhkhjkdsk80i908
Kjhbdd987e68e6ghjbsdkjhgj_J90823020sdgj@#%^& (*&^%d_#$^&(hgjhkhjkdsk80i908 will
be final password(concatenation of above three levels)
(b). Probability of breaking the security
MLC is described in [24]. Table 4 below shows the experimental of MLC with N=1,2,3,4 values
and its corresponding meaning, result with suitable conclusion. Figure 5 presents fully secure
channel as increased level with differing techniques.
Table 4: Secure channel with MLC
Values Meaning P(B)/P(S)=1/2N= Formula
Result
Conclusion
N=0 No security 1 certain unsecure channel
N=1 Single level encryption 0.5 Chance to make it unsecure
N=2 cryptography with lock 0.25 Difficult to unsecure
N=3 cryptography, lock and metadata 0.125 Unlikely to unsecure
N=4 2level cryptography , lock and metadata
0.0625 Fully secure channel
Figure 5: MLC Secure Chanel
Comparison of multi-level authentication with single level authentication when brute force
attacks and dictionary attacks happen for 10 to 10000 times. Shown below is the derived formula
to compare single level attacks and multilevel attacks for 10 - 10000. N times [24], where,
n=number of times attacks, j = number of success, p = probability of success in each
try .The comparison graph is shown in figure 6.

48
Figure 6: comparison graph between single and multilevel
5. SCT PROTOCOL IMPLEMENTATION MODULES
This section describes SCTP implementation modules. In software engineering, UML class
diagram is very well used to represent the system before actual software development. Hence, we
use a class diagram to represent the SCTP implementation modules. Class diagram describes a
SCTP object that shares the same attributes, operations, relationships, and semantics.
Figure 7: SCTP class diagram
10to10000attcks
Probability of breaking single and multi level(3)
0
1

49
Figure 7 shows the SCTP class diagram where major modules of the protocol are presented as
classes. SCTP is the main class which has MDP, MLA and MLC as subclasses. SCTP attributes
are derived from sub classes called constructors. Each constructor initiates the class objects to
perform the MDP, MLA and MLC operations.
6. SCT PROTOCOL CONFORMANCE TESTING
This section describes the SCTP testing suites, which confirm the requirement of SCTP. It also
presents verification and validation test cases for SCTP. It describes the major positive, negative
and security test cases required to test protocol. Basic functionality verifications, testing with
negative values and security test have been done. Test cases are derived from major
functionalities of SCTP i.e MLC, MDP and MLC. Hence, completeness of test cases can be
confirmed by Table 5,containing 20 major test cases. It tests the SCTP MDP, MLA and MLC
functionalities. Test cases prefixed with MDP refer to MDP basic functionalities. Test cases
prefixes with MLA refer to MLA basic functionalities. Test cases prefixed with MLC refer to
MLC basic functionalities. Hence, it confirms the complete SCTP Testing.
Table 5: SCTP functionality test cases
Sl.No# Test Case And Type Description Expected Result
1. MDP_GENERATE , ‘+’ve MDP operation to
generate MDP
The function should
create MDP password
by taking confidential
inputs.
2. MDP_AUTHENTICATE, ‘+’ve MDP operation to
authenticate MDP
The function must
authenticate the given
password with MDP
password
3. MLA_LEVEL_MOVE, ‘+’ve MLA operation to
move the levels
Levels should move to
its inner level as MDP
authenticates
4. MLA_PASSWORD_FLOW, ‘+’ve PF operation to carry
passwords from one
level to the next level
The password should
carry to its lower level
when successfully
authenticates happens
at a higher level.
5. MLA_ALLOW_ACCESS_ATEND,
‘+’ve
Allow operation to get
successful access
After clearing all levels
with a valid password,
user must be able to
access the service
6. MLC_CREATE, ‘+’ve MLC operation to
create secure channel
Must create a secure
channel by generating
cipher texts
7. MDP_NO_INPUT, ‘-‘ ve Test with no inputs
and random texts
It should be able to
generate an error
message to get
confidential inputs
8. MLA_NULL_AUTHENTICATE, ‘-‘
ve
Test with null It should not
authenticate the null

50
password and must
trigger an error
message
9. MLA_NULL_PASSWORD_LEVEL
MOVEMENT, ‘-‘ ve
Test to move levels
with null value
No level should move
when null MDP enters
10. MLA_INVALID_INPUTS, ‘-‘ ve Test with random
invalid inputs
Must notify the vendor
and customer about
invalid input try ( true
positive)
11. MLA_DIRECT_LEVEL_JUMP,
security
Test to jump to lower
level directly
Must not allow to jump
lower levels and trigger
true positive
12. MLC_DIRECR_LEVEL_JUMP
security
Test to jump higher
levels directly
Must not allow for
higher level operation
and trigger true
positive
13. MLA_ZERO_LEVEL
‘-‘ ve
Test with 0 value for
in MLA
Should generate error
message to initiate
MLA levels when it is
zero
14. MLC_ZERO_LEVEL, ‘-‘ ve Test with 0 value in
MLC
message to initiate
MLC levels when it is
zero
15. MLC_NO_METADATA, ‘-‘ ve Test with 0
METADATA value
message to initiate
MLC Metadata when
it has no value
16. MLC_NO_LOCK_KEY, ‘-‘ ve Test with no lock key
and unlock key
message to initiate
MLC lock/unlock key
when it has no value
17. MLC_ NO_CRYPTO_KEY, ‘-‘ ve Test with no
encryption/decryption
key
message to initiate
MLC crypto key when
it has no key value
18. MLC_LOCK_UNLOCK, ‘+’ ve LOCK/UNLOCK
operation for locking
and unlocking files
MLC LOCK and
Unlock operation must
execute properly
19. MLC_METADATA, ‘+’ ve Operation to
arrange/rearrange data
The MLC Metadata
operation must arrange
/ rearrange properly.
20. MLC_RM_CRYPTOGRAPHY
Cancel, security
Test to remove MLC
operation for ML
cryptography
MLC cryptography
must create an error
message and trigger
true positive

51
7.CONCLUSION AND FUTURE ENHANCEMENT
Secure cloud transmission protocol can be used in a cloud computing, transaction where the
strong authentication and secure channel are the mandatory requirements from the customer. It
can be used as add on to the existing HTTP protocol. SCTP achieves strong authentication by
means of MDP_MLA system. SCTP achieves secure channel by means of MLC. This protocol
solves access rights, authentication, privilege, access, authorization, privacy , confidential issues
and achieves customer trust and satisfaction. SCTP is also a solution to brute force attacks,
dictionary attack, phishing attack and it provides strong security. This protocol can be enhanced
by adding usage profile- based intruder detection and prevention system. This paper can be
further enhanced with detailed investigation, comparisons, usefulness and advantages of proposed
techniques.
ACKNOWLEDGMENT
Our sincere thanks to Prof. K N B Murthy, Principal and Prof. Shylaja S S, HOD, Department of
Information Science and Engineering, PES Institute of Technology, Bangalore, for their constant
encouragement.
REFERENCES
[1] Security and Privacy Issues in Cloud Computing, Innovation Labs, Jaydip Sen, Tata Consultancy
Services Ltd., Kolkata, INDIA,2011-13.
[2] Cloud and Security Research Lab HP Labs Privacy, Security and Trust Issues Arising from Cloud
Computing, Siani Pearson and Azzedine Benameur, 2nd IEEE International Conference on Cloud
Computing Technology and Science, 978-0-7695-4302-4/10,693-792.
[3] Accenture Technology Labs, Accenture Bangalore, India, Cloud Computing Security - Trends and
Research Directions, Shubhashis Sengupta, Vikrant Kaulgud, Vibhu Saujanya Sharma, 2011 IEEE
World Congress on Services, IEEE computer Society,978-0-7695-4461-8/11,524-531.
[4] Ponemon Institute, Security of Cloud Computing Users Study, CA Technologies Independently
conducted by Ponemon Institute, LLC Publication Date: March 2013
[5] A quantitative analysis of current security concerns and solutions for cloud computing, Nelson
Gonzalez1*, Charles Miers1,4, Fernando Red´ıgolo1, Marcos Simpl´ıcio1, Tereza Carvalho1, Mats
N¨aslund2 and Makan Pourzandi3, springer , Gonzalez et al. Journal of Cloud Computing: Advances,
Systems and Applications 2012, 1:11
[6] Security Analysis of Authentication Protocols for Next-Generation Mobile and CE Cloud Services,
Slawomir Grzonkowski and Peter M. Corcoran, Thomas Coughlin, 2011 IEEE International
Conference on Consumer Electronics - Berlin (ICCE-Berlin), 978-1-4577-0234-1/11, 83-87.
[7] A Gossip Protocol for Dynamic Resource Management in Large Cloud Environments, Fetahi Wuhib,
Rolf Stadler, and Mike Spreitzer, IEEE TRANSACTIONS ON NETWORK AND SERVICE
MANAGEMENT, VOL. 9, NO. 2, 1932-4537, 213-225,June-2012.
[8] An Efficient and Secure Dynamic Auditing Protocol for Data Storage in Cloud Computing, Kan
Yang, Xiaohua Jia, IEEE TRANSACTIONS ON PARALLEL AND DISTRIBUTED SYSTEMS,
VOL. 24, NO. 9, SEPTEMBER 2013, 1717-1726.
[9] Access Protocols in Data Partitioning Based Cloud Storage, Yunqi Ye, Liangliang Xiao, Yinzi Chen,
I-Ling Yen, Farokh Bastani , Ing-Ray Chen, 2013 IEEE Sixth International Conference on Cloud
Computing, 978-0-7695-5028-2/13, 398-397, 2013.
[10] A Collaborative Fault-Tolerant Transfer Protocol for Replicated Data in the Cloud,IEEE transaction,
Nader Mohamed and Jameela Al-Jaroodi, 978-1-4673-1382-7/12, 203-210, 2012.

52
[11] Applying an Agent-Based User Authentication and Access Control Model for Cloud Servers, Mostafa
Hajivali , Faraz Fatemi Moghaddam , Maen T. Alrashdan , Abdualeem Z. M. Alothmani , ICTC
2013, 978-1-4799-0698-7/13, 807-902,2013.
[12] “Enabling Public Auditability and Data Dynamics for Storage Security in Cloud Computing,” Q.
Wang, C. Wang, K. Ren, W. Lou, and J. Li, IEEE Trans. Parallel Distributed Systems, vol. 22, no.
5,pp. 847-859, May 2011.
[13] “Privacy-Preserving Public Auditing for Data Storage Security in Cloud Computing,”, C. Wang, Q.
Wang, K. Ren, and W. Lou, Proc. IEEE INFOCOM, pp. 525-533, 2010
[14] Authentication and secured execution for the Infrastructure-as-a-Service layer of the Cloud
Computing model, Laurent Hubert, Renaud Sirdey, 2013 Eighth International Conference on P2P,
Parallel, Grid, Cloud and Internet Computing, 978-0-7695-5094-7, 291-296, 2013.
[15] Authentication Using Graphical Password in Cloud, Ming-Huang Guo, Horng-Twu Liaw, Li-Lin
Hsiao, Chih-Ta Yen, 177-181, 2013.
[16] A secure biometric-based authentication scheme using smart card,IEEE, H. B. Tang*, Z. J. Zhu, Z.
W. Gao, Y. Li, 39-43,2013.
[17] “Analysis and improvement on an efficient biometric-based remote user authentication scheme using
smart cards”, A. K. Das. IET Information Security, 5 (3), pp. 145-151, 2011.
[18] Cloud-based RFID Authentication, Wei Xie1, Lei Xie2, Chen Zhang1, Quan Zhang1, Chaojing
Tang1, 2013 IEEE International Conference on RFID, 978-1-4673-5750-0/13,168-175, 2013.
[19] secure cloud authentication using eids, bernd zwattendorfer, arne tauber, proceedings of ieee
ccis2012, 978-1-4673-1857-0/12/, 397-401, 2012.
[20] A User Identity Management Protocol for Cloud Computing Paradigm Safiriyu Eludiora1, Olatunde
Abiona2, Ayodeji Oluwatope1, Adeniran Oluwaranti1, Clement Onime3,Lawrence Kehinde
apered in Int. J. Communications, Network and System Sciences, 2011, 4, 152-163
[21] “Framework Design of Secure Cloud Transmission Protocol”, Dinesha H A, Dr. V. K Agrawal, IJCSI
International Journal of Computer Science Issues, Vol. 10, Issue 1, No 1, January 2013, ISSN (Print):
1694- 0784 | ISSN (Online): 1694-0814,74-81.
[22] “Multi-dimensional Password Generation Technique for accessing cloud services”, Dinesha H A, Dr.
V. K Agrawal, Special Issue on: "Cloud Computing and Web Services", International Journal on
Cloud Computing: Services and Architecture (IJCCSA), Vol.2, No.3, June 2012, 31-39.
[23] “Multi-level Authentication Technique for Accessing Cloud Services”, Dinesha H A,
Dr.V.K.Agrawal, IEEE International Conference on Computing, Communication and Applications
(ICCCA-2012), Dindigul, Tamilnadu, India, 22-24 February 2012, 978-1-4673-0270-8, 1 – 4.
[24] “Multilevel Cryptography with Metadata and Lock Approach for Storing Data in Cloud”, Dinesha H
A, Dr.V.K Agrawal, Springer Journal of Cryptographic Engineering (JCEN) (submitted).
[25] “Usage Profile Based Intruder Detection System for accessing cloud service”, Dinesha H A, Dr.V.K
Agrawal, Transactions on Networks and Communications, Volume 2, Issue 6, 10.14738/tnc.26.590.
Dec 2014.
[26] “Cloud Computing – Phone Call as a Service: A Concept”, Ms. R Monica, Mr.Dinesha H.A,
Prof.V.K Agrawal, to IEEE Internl.. Conference on Advances in Computing, Communications and
Informatics (ICACCI-2013), 978-1-4799-2432-5, 13861185, 22-25 Aug. 2013, 236 – 242.
[27] “Wireless Sensor-Cloud Integration Using Ant Colony Routing Algorithm”, R. Monica, Dinesha H A,
Dr.V.K Agrawal, International Conference on cloud computing and service engineering
(CLUSE2012), held at Raja Rajeshwari College of Engineering & KINGSTON, UK, 11-13 April
2012, 294-298, Received Best Paper Award, Referred to ISEEC Journal.
[28] “Formal Modeling for Multi-Level Authentication in Sensor-Cloud Integration System”. Dinesha H
A, R Monica and V.K. Agrawal. International Journal of Applied Information Systems 2(3) (IJAIS)
Published by Foundation of Computer Science, New York, USA, May 2012, 16-21.
[29] Adaptive Password-Strength Meters from Markov Models, Claude Castelluccia, Markus D¨urmuth,
Daniele Perito.

DEVELOPMENT OF SECURE CLOUD TRANSMISSION PROTOCOL (SCTP) ENGINEERING PHASES : MULTILEVEL SECURITY & CRYPTOGRAPHY

Recommended

More Related Content

What's hot (20)

Viewers also liked (19)

Similar to DEVELOPMENT OF SECURE CLOUD TRANSMISSION PROTOCOL (SCTP) ENGINEERING PHASES : MULTILEVEL SECURITY & CRYPTOGRAPHY (20)

Recently uploaded (20)

DEVELOPMENT OF SECURE CLOUD TRANSMISSION PROTOCOL (SCTP) ENGINEERING PHASES : MULTILEVEL SECURITY & CRYPTOGRAPHY