System administrator and cloud support engineer

2-3 years

We are looking for a capable System Administrator to take over all aspects of the configuration and maintenance of computer systems. A System Admin should be able to diagnose and resolve problems quickly and should have the patience to communicate with a variety of interdisciplinary teams and users.

Monitoring and reporting all points mentioned below.

Ensure Security updates are installed:

  • Regularly checking whether the Antivirus software is updated for users.
  • Regularly monitor platforms like Google to ensure everybody is using up-to-date applications with no security issues.
  • Regularly Email users about the security updates that they need to install on their laptops and PCs.


Centrally managed antivirus should be installed on all laptops and mobile devices. 

  • Adding a purchase request for any additional licence that we might require.
  • Pushing new software updates on users’ laptops.
  • Keeping up-to-date with antivirus updates so all our devices are secure.
  • Miradore user agent.

Mobile device and access management

  • Set rules and configure settings on personal and organisation-owned devices to access data and networks.
  • Deploy and authenticate apps on devices -- on-premises and mobile.
  • Protect company data by controlling the way users access and share information.
  • Make sure devices and apps are compliant with security requirements.
  • Only provide user access to laptops (No admin access, excluding developers).
  • All new software installation requests will go through the system admin to make sure nothing is installed on work laptops that poses a security risk.

Vanta compliance-related tickets

  • Vanta will continue to monitor and create issues to be compliant with ISO 27K over time. The system administrator must resolve all such system-related tickets.

Access management to different user applications

  • Access should be restricted to only what is necessary to perform job duties ("principle of least privilege").
  • Technical access to all the company’s networks must be formally documented, including the standard role for approver, grantor, and date.
  • Only authorised employees and third parties working off a signed contract or statement of work, with a business need, shall be granted access to the company’s production networks.

Guest network management

The company’s guests may be granted access to guest networks after registering with office staff without a documented request - guest network management.

  • Remote connections to production systems and networks must be encrypted.
  • Administrators should verify that the account does not violate any organisation’s security or system access control policies, such as segregation of duties, fraud prevention measures, or access rights restrictions.
  • Records of all permission and privilege changes shall be maintained for no less than one year.
  • Administrators must review the access rights of users, administrators, and service accounts on a quarterly basis to verify that user access is limited to systems that are required for their job function.

Removal media encryption

  • Research removable media encryption and figure out if removable media should be implemented and make sure it is always encrypted.

MFA reset and debugging

As we are enabling MFA for more and more applications that we have, more people are likely to have issues with it as the business moves forward. 

  • Different online applications will have different ways of handling the MFA reset; a system admin should be familiar with all.

Website watcher configuration and email issues

  • Software like Website Watcher keeps having email issues, as it sends emails in huge numbers every day. The system administrator must keep an eye on the emails and fix issues promptly as and when they arise.

Office network management

  • System admin can help in creating guest networks in the office and making sure that the network is as secure as possible.

Phishing emails

  • Finding the optimal solution to prevent phishing emails from getting delivered.
  • Verifying emails sent by our staff to check for phishing emails.

Security incidents handling

  • System admin must monitor incident and event tickets and assign severity tickets.
  • Continuous checks to ensure the security incident policies are being followed and up to date
  • A root cause analysis report must be documented and referenced in incident tickets.
  • A central "War Room" will be designated for handling security threats. This may be a physical or virtual location  (i.e., Slack channel) and managed by the system admin.

Conducting recurring Incident Response Meetings until the incident is resolved

  • Legal and executive staff will be informed as needed
  • Update Incident Tickets and timelines
  • Document new Indicators of Compromise (IOCs)
  • Perform investigative Q&A
  • Apply emergency mitigations
  • Plan long-term mitigations
  • Document Root Cause Analysis (RCA)
  • Additional items as needed
  • All incidents shall be formally documented, and a documented root cause analysis shall be performed.
  • The Incident Response Plan shall be reviewed and tested at least annually.

Implement password policy

  • Password policy must be in place to ensure that users are using secure passwords that are not easily crackable.


  • DevOps is a plus point