Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
Contents
Requirements (Omi)..............................................................................................................................1
Gantt Chart............................................................................................................................................1
Risk Assessment and solutions:.............................................................................................................2
Design Solutions: (Andrian)...................................................................................................................3
USER 2...................................................................................................................................................4
USER 3...................................................................................................................................................4
USER 4...................................................................................................................................................4
USER 5...................................................................................................................................................4
IT ACCOUNT ADMINISTRATOR:..............................................................................................................5
This is how it would be represented through a diagram:......................................................................5
Implementation: (Damola)....................................................................................................................7
User Assessment: (Afsar).....................................................................................................................11
Feedback and Review: (Redeemer).....................................................................................................18
Feedback from the improvement:.......................................................................................................23
Final review (Afsar):.............................................................................................................................23
Reference:...........................................................................................................................................24
Part B: Design and deploy a cloud-based collaboration service to
meet a client’s needs
Part C: Manage and review a cloud-based collaboration service to
meet a client’s needs
Requirements (Omi)
Create a collaboration system that allows 5 users to collaborate in the cloud-based storage
areas and they include:
Being able to share calendar appointments
Being able to use at least 2 different browsers from desktop operating system.
Being able to use at least 1 browser from mobile operating system.
Being able to share word processing documents and spreadsheets that will also
allow users to collaborate at the same time.
Gantt Chart
Will be using Gantt Chart that will help us manage our time and schedule tasks that will
allow us to work more productively and efficient. Here is the Gantt Chart:
1|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
Reason of using this Gantt Chart is to plan out this project’s timetable, we have split it into
reasonable categories and have provided a covered time coverage of how long its duration
will last.
We plan to use a maximum of 2 days of Research and Planning to maximize time efficiency
and provide a clear description on what we should do for our project.
We will use 2 days to plan out any requirements as well as costs for the duration of this
project, a reasonable amount of time to plan out any requirements we will require through-
out the project as well maintain costs within the budget of this project.
Both Designing and Implementation parts will require some time for completion, since we
will be applying the project and setting it up for the company to use. This will take some
time as designing and implementation of that design may take a few weeks since it is a huge
transition from serverless options to cloud-based operations. Hence why, it will be
necessary to give our people some time to manage the given task.
Testing and Optimisation will be based on how complex the final design will be, as well as
how the implementation will go, that directly corelates towards how complex the final
design will be. Mostly, testing and optimisation will consist in security tests, optimisation of
the system for beginners or people in need of advice on how to work on with the newly
based cloud system.
Final Testing will consist of final adjustments made to the cloud-based system for the
company, work around its specifications, add the final pieces of the project and wait for
Feedback and Reviews from the company itself about how this newly cloud-based system
will treat them.
Feedback and Review are crucial when attempting to call the project either a success or a
failure, depending on how the company views the cloud-based system, will also impact our
overall work, and determine if we should continue the project and continue to brainstorm
ideas on how to impress the company and have the system be of their liking.
Risk Assessment and solutions:
1. One way to increase security of employee’s passwords and eliminate the potential of
getting hacked would be to implement a strong password policy, the passwords
should contain more than 12 digits, it should also contain at least one Upper case
letter and lowercase letters; it also must contain at least 1 number and symbols. This
2|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
is to ensure that employees don’t accidentally get hacked by unwanted people by
using a poorly secure password for their access to the cloud-based system.
2. All the employee’s accounts will have 2 Step Verification enabled that will add
another layer of security and prevent unauthorized access even if the hacker has
cracked the password as they will also have to verify through SMS verification or
Google authenticator to gain access to the account.
3. All passwords in the company must be changed every month, this is to maintain
security and have the upper edge on people who are trying to password guess
employees’ accounts to gain unwanted access to company files on the cloud.
4. At the attempt of the user’s first login, they should be immediately prompted to
change their password, as the password given to them would most likely be very
simple and could easily be password guessed by unwanted people, therefore this is
to make sure that users will change their passwords as soon as they were able to
login through the given account email address and temporary password (by
following criteria 1.).
5. Users should only be allowed to login through the company’s provided mobile
devices and computers, as allowing access to logins from different areas that are
outside of the company would not be as secure, and you would not be able to know
where this login has taken place without the account administrator checking its
recent login sessions and from where it took place.
6. A daily inspection of company computers should take place as not only it would
eliminate risks of malware potentially getting into the mobile devices and
computers, but it would also ensure that every user in the company has successfully
logged out of their accounts and have turned off the computers, sometimes this can
be one of the ways how a company get their data and files stolen off, simply by not
paying attention to their company devices connected to the cloud-based system.
Design Solutions: (Andrian)
(A) We will be opening Google accounts to access Google Drive for the company:
The accounts are as follows:
USERS:
USER 1
Username:
Password: CBS12345
Condition: USER 1 should immediately change the password upon first login into the cloud-based
system.
Password policies: USER 1 should change their password for their own account every month and
create a difficult and strong password that follows the password policies: Passwords should contain
more than 12 digits, it should also contain at least one Upper case letter and lowercase letters; it
also must contain at least 1 number and symbols.
3|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
USER 2
Username:
Password: CBS12345
Condition: USER 2 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 2 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 3
Username:
Password: CBS12345
Condition: USER 3 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 3 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 4
Username:
Password: CBS12345
Condition: USER 4 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 4 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 5
Username:
Password: CBS12345
Condition: USER 5 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 5 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
4|Page
, Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
These accounts will be created to access the cloud-based system, in this case we will be
using Google’s Google Drive and provide these accounts with upmost possibility of storage
to store files, depending on how big the company is, will also determine monthly costs of
the storage amount; currently Google Drive allows a Free amount of storage which is 5 GB
of storage, but they also offer 200 GB, 2 TB, 5 TB, 10 TB, 20 TB and 30 TB of storage space,
so depending on how big the company is will also depend on how much you are willing to
spend on cloud-based server storage.
We will be using Google Drive due its highly advanced security options for Google users as
well as protection of data, it will be an outsourced IT provider but a trustable outsource
service for the company, as not only it is reputable company, but they also provide the
upmost highest security in terms of account protection and safety.
(A) We will create an account administrator and manager, that will maintain and
manage access for the 5 staff accounts.
IT ACCOUNT ADMINISTRATOR:
Username:
Password: @95*"P+ZQuBZWSq2
IT sector: Administrator and Owner of the account.
Password policies: Passwords should contain more than 12 digits; it should also contain at
least one Upper case letter and lowercase letters; it also must contain at least 1 number
and symbols. MUST BE CHANGED EVERY 2 WEEKS.
This is how it would be represented through a diagram:
5|Page
Contents
Requirements (Omi)..............................................................................................................................1
Gantt Chart............................................................................................................................................1
Risk Assessment and solutions:.............................................................................................................2
Design Solutions: (Andrian)...................................................................................................................3
USER 2...................................................................................................................................................4
USER 3...................................................................................................................................................4
USER 4...................................................................................................................................................4
USER 5...................................................................................................................................................4
IT ACCOUNT ADMINISTRATOR:..............................................................................................................5
This is how it would be represented through a diagram:......................................................................5
Implementation: (Damola)....................................................................................................................7
User Assessment: (Afsar).....................................................................................................................11
Feedback and Review: (Redeemer).....................................................................................................18
Feedback from the improvement:.......................................................................................................23
Final review (Afsar):.............................................................................................................................23
Reference:...........................................................................................................................................24
Part B: Design and deploy a cloud-based collaboration service to
meet a client’s needs
Part C: Manage and review a cloud-based collaboration service to
meet a client’s needs
Requirements (Omi)
Create a collaboration system that allows 5 users to collaborate in the cloud-based storage
areas and they include:
Being able to share calendar appointments
Being able to use at least 2 different browsers from desktop operating system.
Being able to use at least 1 browser from mobile operating system.
Being able to share word processing documents and spreadsheets that will also
allow users to collaborate at the same time.
Gantt Chart
Will be using Gantt Chart that will help us manage our time and schedule tasks that will
allow us to work more productively and efficient. Here is the Gantt Chart:
1|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
Reason of using this Gantt Chart is to plan out this project’s timetable, we have split it into
reasonable categories and have provided a covered time coverage of how long its duration
will last.
We plan to use a maximum of 2 days of Research and Planning to maximize time efficiency
and provide a clear description on what we should do for our project.
We will use 2 days to plan out any requirements as well as costs for the duration of this
project, a reasonable amount of time to plan out any requirements we will require through-
out the project as well maintain costs within the budget of this project.
Both Designing and Implementation parts will require some time for completion, since we
will be applying the project and setting it up for the company to use. This will take some
time as designing and implementation of that design may take a few weeks since it is a huge
transition from serverless options to cloud-based operations. Hence why, it will be
necessary to give our people some time to manage the given task.
Testing and Optimisation will be based on how complex the final design will be, as well as
how the implementation will go, that directly corelates towards how complex the final
design will be. Mostly, testing and optimisation will consist in security tests, optimisation of
the system for beginners or people in need of advice on how to work on with the newly
based cloud system.
Final Testing will consist of final adjustments made to the cloud-based system for the
company, work around its specifications, add the final pieces of the project and wait for
Feedback and Reviews from the company itself about how this newly cloud-based system
will treat them.
Feedback and Review are crucial when attempting to call the project either a success or a
failure, depending on how the company views the cloud-based system, will also impact our
overall work, and determine if we should continue the project and continue to brainstorm
ideas on how to impress the company and have the system be of their liking.
Risk Assessment and solutions:
1. One way to increase security of employee’s passwords and eliminate the potential of
getting hacked would be to implement a strong password policy, the passwords
should contain more than 12 digits, it should also contain at least one Upper case
letter and lowercase letters; it also must contain at least 1 number and symbols. This
2|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
is to ensure that employees don’t accidentally get hacked by unwanted people by
using a poorly secure password for their access to the cloud-based system.
2. All the employee’s accounts will have 2 Step Verification enabled that will add
another layer of security and prevent unauthorized access even if the hacker has
cracked the password as they will also have to verify through SMS verification or
Google authenticator to gain access to the account.
3. All passwords in the company must be changed every month, this is to maintain
security and have the upper edge on people who are trying to password guess
employees’ accounts to gain unwanted access to company files on the cloud.
4. At the attempt of the user’s first login, they should be immediately prompted to
change their password, as the password given to them would most likely be very
simple and could easily be password guessed by unwanted people, therefore this is
to make sure that users will change their passwords as soon as they were able to
login through the given account email address and temporary password (by
following criteria 1.).
5. Users should only be allowed to login through the company’s provided mobile
devices and computers, as allowing access to logins from different areas that are
outside of the company would not be as secure, and you would not be able to know
where this login has taken place without the account administrator checking its
recent login sessions and from where it took place.
6. A daily inspection of company computers should take place as not only it would
eliminate risks of malware potentially getting into the mobile devices and
computers, but it would also ensure that every user in the company has successfully
logged out of their accounts and have turned off the computers, sometimes this can
be one of the ways how a company get their data and files stolen off, simply by not
paying attention to their company devices connected to the cloud-based system.
Design Solutions: (Andrian)
(A) We will be opening Google accounts to access Google Drive for the company:
The accounts are as follows:
USERS:
USER 1
Username:
Password: CBS12345
Condition: USER 1 should immediately change the password upon first login into the cloud-based
system.
Password policies: USER 1 should change their password for their own account every month and
create a difficult and strong password that follows the password policies: Passwords should contain
more than 12 digits, it should also contain at least one Upper case letter and lowercase letters; it
also must contain at least 1 number and symbols.
3|Page
,Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
USER 2
Username:
Password: CBS12345
Condition: USER 2 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 2 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 3
Username:
Password: CBS12345
Condition: USER 3 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 3 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 4
Username:
Password: CBS12345
Condition: USER 4 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 4 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
USER 5
Username:
Password: CBS12345
Condition: USER 5 should immediately change the password upon first login into the cloud-
based system.
Password policies: USER 5 should change their password for their own account every month
and create a difficult and strong password that follows the password policies: Passwords
should contain more than 12 digits, it should also contain at least one Upper case letter
and lowercase letters; it also must contain at least 1 number and symbols.
4|Page
, Made by: Andrian, Afsar, Damola, Redemer, Damola Unit 16: Cloud Storage and Collaboration Tools (Part B and C)
These accounts will be created to access the cloud-based system, in this case we will be
using Google’s Google Drive and provide these accounts with upmost possibility of storage
to store files, depending on how big the company is, will also determine monthly costs of
the storage amount; currently Google Drive allows a Free amount of storage which is 5 GB
of storage, but they also offer 200 GB, 2 TB, 5 TB, 10 TB, 20 TB and 30 TB of storage space,
so depending on how big the company is will also depend on how much you are willing to
spend on cloud-based server storage.
We will be using Google Drive due its highly advanced security options for Google users as
well as protection of data, it will be an outsourced IT provider but a trustable outsource
service for the company, as not only it is reputable company, but they also provide the
upmost highest security in terms of account protection and safety.
(A) We will create an account administrator and manager, that will maintain and
manage access for the 5 staff accounts.
IT ACCOUNT ADMINISTRATOR:
Username:
Password: @95*"P+ZQuBZWSq2
IT sector: Administrator and Owner of the account.
Password policies: Passwords should contain more than 12 digits; it should also contain at
least one Upper case letter and lowercase letters; it also must contain at least 1 number
and symbols. MUST BE CHANGED EVERY 2 WEEKS.
This is how it would be represented through a diagram:
5|Page
