1) 2FA

To enable authentication app 2-factor authentication for your individual

account:

1. Click on your account icon in the top-right corner of the page and select Account
Settings.
2. In the navigation panel on the left side of the screen, click “Security.”

3. Scroll down to the "Signing in to Google" section, and click "2-Step

Verification."
4. Then click "Get started" and

5. Enter you mobile Phone number and Choose whether you want to use "Voice
Call " or "text message" though We recommends the former.
Click on “NEXT”
 6. Enter you mobile Phone number and Choose whether you want to use
"Google prompts" or "Voice or text message," though Google recommends the
former

7. Follow the on-screen instructions to set up two-factor authentication. If you're

unable to set up this feature, please contact your administrator.

Project Plan

1. Campaign and train

Transition 2fa must be treat as a marketing campaign where we need to sell

employees on the idea – as well as provide training opportunities along the way. It
is important for staff to understand that 2FA is there to support then and protect
their accounts and all their data, because that may not be their first thought when
met with changes to the way they sign in to the tools they use every day.

We must focus on informing users, explaining why we are making this change -
making it very clear what they will need to do and where they can find
instructions, documentation, and support.

2. Start with admin accounts

At a minimum, we want to use 2FA for all our admins, so we will start with
privileged users. Administrative accounts are our highest value targets and the
most urgent to secure, but we can also treat them as a proof of concept for
wider adoption.
Review who these users are and what privileges they have—there are
probably more accounts than we expect with far more privileges than are
really needed.

At the same time, we must look at key business roles where losing access to
email—or having unauthorized emails sent—will have a major security impact.

3. Plan for wider deployment

To Schedule a planning for the other users after succeeding with the admin
accounts

4. Have a support plan

Plan how we will handle failed sign-ins and account lockouts. Even with
training, some failed sign-ins will be legitimate users getting it wrong and you
need to make it easy for them to get help.
 We also need to quickly get them connected another way so they can get back
to work. We have to register more than one device so the users have an
alternative sign-in method

5. Measure and monitor

As we deploy 2FA, we have to monitor the rollout to see what impact it has on
both security and productivity and be prepared to make changes to policies or
invest in better hardware to make it successful.
We must track security metrics for failed login attempts, credential phishing
that gets blocked and privilege escalations that are denied.

2. Ticketing

1. Step 1: Define the Goals. ...

2. Step 2: Understand User Expectations & Pain Points. ...
3. Step 3: Onboard & Train the Agents. ...
4. Step 4: Create Predefined Rules for an Automated Workflow. ...
5. Step 5: Create a User-Centric Knowledge Base. ...
6. Step 6: Target the Right KPIs.

3. Troubleshooting

1. Gather information. Gathering information is a logical first step in

any troubleshooting endeavor. ...
2. Understand the malfunction. ...
3. Identify the source of the incident. ...
4. Correct/repair the incident. ...
5. Verify the repair. ...
6. Perform root cause analysis.