Cloud Infrastructure and Cybersecurity

Start with who needs safe cloud set-up and security monitoring and why. Around small firms and public bodies drive demand in Dubai, Abu Dhabi and the other emirates.

• List 10 offers or suppliers in the UAE with price per client month in AED and who buys.
• Interview 5 people from small firms and public bodies: what do they buy now, how often, what do they pay, what annoys them?
• Learn three terms: Least privilege (giving each person only the access they need); Multi-factor sign-in (a second proof such as a code); Restore test (proving a backup really works).
• Write a one-page brief: user, need, hoped-for price, and the rule that matters most.

Activity. Complete the market table, five interview notes and the brief.

Standard to meet. Price ten offers, interview five users, and state one need in one sentence.

Know the rule before the work. Main hazards here: data theft, ransom attacks and weak passwords. Hazard thinking means list each step, ask what could go wrong, and decide the control.

• Ask your local authority or free zone which licence, permit or inspection applies. Write the answer and the date you asked.
• For each step (inventory assets; set up access; back up; monitor and respond; review) write the hazard and the control.
• Use a hierarchy: remove the hazard, replace it, separate people from it, change the way of work, then protective equipment last.
• Keep a one-page incident rule: who you call, what you stop, what you record.

Activity. Draw the flow and mark hazard and control at each step.

Standard to meet. Name a hazard and a control for every step, and answer the licence question in writing.

The work is a short chain: inventory assets, set up access, back up, monitor and respond, review. Learn each link, then link them with records.

• Write a checklist for each of the 5 steps: input, action, check, output.
• Time each step three times and note the slowest.
• Record a defect or delay each time it happens: what, where, cause, fix.
• Measure time to detect and fix an incident, in minutes; this is your main number.

Activity. Run the chain three times (simulated or real) and fill the log.

Standard to meet. Complete three logs, and give the slowest step a cause and a fix.

What you do not measure you cannot improve. Your main measure is time to detect and fix an incident, in minutes.

• Define time to detect and fix an incident, in minutes: what counts, what does not, and over what period.
• Draw a simple chart of the last 10 results and mark the average.
• Find the top two causes of loss with a tally sheet, then fix the biggest one first.
• Check measuring tools: are they accurate, clean and in date?

Activity. Collect a tally for one week and make a Pareto chart.

Standard to meet. Complete the tally, name the biggest cause, and plan one fix with a date.

Know the cost of one client month before you set the price. Include materials, labour, energy, transport, licence share, waste and a safety margin.

• Cost per client month = total cost divided by client months sold (not made).
• Margin = (price minus cost) divided by price.
• Break-even units = fixed costs divided by gain per unit.
• Test the price with two users and write down the answer.

Activity. Build the cost sheet with AED on every line and have your mentor check it.

Standard to meet. Check that no cost is missing, and calculate the margin twice by different routes.

Customers return when you keep promises. Promise only what your workflow can deliver.

• Write a one-page offer: what is included, what is not, price, time, how you fix mistakes.
• Write a short script for the first call or visit.
• Agree dates in writing; confirm each change.
• Handle a complaint in four steps: listen, apologise for the impact, fix, record what changed.

Activity. Present the offer to two users and note changes.

Standard to meet. Write an offer with scope, price, time and a fix rule, and collect comments from two users.

Small, real and recorded. Change one thing at a time and learn quickly.

• Keep a daily log: date, units, cost, delays, defects, safety notes.
• Hold a 15-minute review each week with your mentor.
• Write down every complaint and what you changed.
• Take photos only where allowed and never of people without consent.

Activity. Complete 30 days of the log and four weekly reviews.

Standard to meet. Log 30 days, give each defect a cause, and keep weekly notes.

A decision beats a feeling. Compare plan with result and choose to scale, change or stop.

• Make a before and after table: cost per unit, defects, delays, repeat users.
• Write three lessons.
• Decide scale, change or stop, with the numbers behind it.
• Give two peers one strength and one fix each.

Activity. Present to a review room and collect one written comment from a user.

Standard to meet. Justify the decision with numbers, and give two peer reviews.

Cloud services are rented by the hour, so a plan needs sums for capacity, cost and backup. Security starts with knowing exactly what you are running.

• List every asset first: servers, storage, databases, user accounts and who owns each. You cannot protect what you have not listed.
• Estimate monthly cost as price per hour x hours running x number of machines, then add storage and data transfer.
• Back up by the 3-2-1 idea: 3 copies, on 2 kinds of storage, 1 held off-site. Set how much data you can afford to lose (in hours) and how fast you must be back (in hours).
• Test a restore, not just the backup. A backup never restored is only a hope.

Activity. Build a cost sheet for a sample set-up of 3 machines and 200 GB storage, and write the restore-test steps for it.

Standard to meet. List every asset with an owner, compute monthly cost with units, and describe and date one restore test.

Most break-ins use stolen or weak passwords, not clever tricks. Good control and clear legal limits protect both the client and you.

• Give each person least privilege: only the access their job needs, removed on the day they leave.
• Turn on multi-factor sign-in for every account that can reach data or change settings; start with administrators.
• Recognise common attacks: phishing messages, ransom software, weak or reused passwords, and unpatched systems.
• Only test or scan systems where you hold written permission that states the scope and dates. Testing without permission can be a crime.

Activity. Review a sample list of 30 accounts supplied by your mentor and produce a ranked fix list with owners and dates.

Standard to meet. Fix leaver accounts and administrators first, date the fixes and touch no live system without written permission.

When something goes wrong, speed matters. Teams measure how long it takes to notice and to fix, then try to shorten both.

• Collect logs from sign-ins, firewalls and servers in one place, with clocks set to the same time.
• Follow the response steps in order: detect, contain, remove the cause, recover, then review what happened.
• Record times: time to detect and time to fix, both in minutes, for every incident.
• Hold a short review after each incident and write down one change that would have stopped or shortened it.

Activity. Calculate average time to detect and fix from a sample incident log of 5 events and suggest one change for each.

Standard to meet. Calculate times in minutes, show steps in the right order and give each review one concrete change.

On the slide: L1 Basic · Cloud assets and passwords

Notes: Name the main parts of a cloud set-up (servers, storage, databases, accounts) and say why a strong password is not enough. Notes: use a simple list of assets with an owner for each; introduce multi-factor sign-in as a second proof such as a code.

On the slide: L2 Awareness · Attacks and permission to test

Notes: Describe common attacks (phishing, ransom software, weak passwords, unpatched systems) and state that you test only systems where you hold written permission. Notes: permission must state the scope and dates; testing without it can be a crime.

On the slide: L3 Foundation · Cost a small cloud set-up

Notes: Calculate the monthly cost of a small set-up from hours, price and storage. Notes: check the practice case of 2 servers for 730 hours at AED 0.40 plus 500 GB at AED 0.09 giving AED 584 + AED 45 = about AED 629 a month.

On the slide: L4 Practitioner · Review accounts and test a restore

Notes: Review a sample list of 30 accounts and write a ranked fix list, then describe a dated restore test. Notes: leaver accounts and administrators come first; 6 of 40 accounts without multi-factor sign-in is 15.0%; use the 3-2-1 backup rule.

On the slide: L5 Specialist · Measure and shorten incident times

Notes: Analyse a log of incidents for time to detect and time to fix in minutes and suggest one change for each. Notes: incident A took 45 minutes to detect and 150 to fix, incident B 20 and 90, so averages are 32.5 and 120 minutes; price check is AED 900 per client month against AED 300 cost, a margin of 66.7%.

On the slide: L6 Advanced · Coach a team on response steps

Notes: Set the response order (detect, contain, remove, recover, review), a leaver rule and a weekly access review for a small team. Notes: disable leaver accounts on the day they leave; sample five incidents a month for times in minutes and one change each.

On the slide: L7 Super expert · Design the whole security system

Notes: Design the asset list, access, backup, monitoring and response controls for 20 client months, audit permission and ransom risks and write a 12-month plan. Notes: present one risk, one saving and quarterly targets for time to detect and time to fix.