Information security and cyber for organizations

Risk management and compliance (GRC), technical protection of the infrastructure, and monitoring and handling of incidents (SOC, incident response), all with the same team that runs the business’s IT. That way security is built into the servers, the network and the permissions, and does not remain a document nobody implements.

Working securely on a laptop in a bright office

Security where you
can see what is happening

We build a clear picture of the business’s security posture: who accesses what, which computers are protected, what has been updated and what needs attention. That way decisions are based on data, not on a hunch.

  • Risk mapping (risk assessment) and a work plan by priority
  • Hardening, EDR and MFA for all users
  • Monitoring, alerts and a rehearsed response procedure (incident response)

Call +972-3-3801180

Who this is for

  • Organizations that hold personal data

    Businesses that hold data about customers, patients or employees, and are therefore subject to the Privacy Protection Law and the data security regulations.

  • Suppliers to large organizations

    That receive security questionnaires from customers and need to show policies, controls and documentation to keep working with them.

  • Businesses without an internal security function

    IT works, but nobody is responsible for the risks, the procedures and what happens on the day there is an incident (incident response).

Sound familiar?

These are situations we see in organizations whose IT works, but whose information security has no owner.

  • There is no clear picture of who accesses which data (access control), and from which computers
  • A large customer sent an information security questionnaire, and nobody knows how to answer it
  • You have heard about Amendment 13, and it is not clear what it requires of the business
  • There is antivirus, but nobody looks at the alerts (SOC)
  • Accounts of employees who left long ago are still active (offboarding procedure)
  • There is no plan for a ransomware attack (incident response plan), and it is not clear who decides what to do

What the information security service includes

The scope depends on the size of the organization, the sensitivity of the data and the regulatory requirements that apply to it.

  • Governance, risk and compliance (GRC)

    A risk assessment and risk register, policies and procedures, and alignment with the Privacy Protection Law, ISO 27001 and NIST CSF.

  • Outsourced CISO

    An owner for information security who supports management, reports to it regularly and runs an annual work plan.

  • Identities and permissions (IAM)

    MFA for all users, minimal permissions (least privilege), LAPS for local administrator accounts and PAM for sensitive access.

  • Endpoint and server protection

    EDR/XDR instead of classic antivirus, hardening of Windows and Active Directory, and security update management (patch management).

  • Network security

    A firewall, web filter, segmentation and ZTNA, so a breach of one workstation does not open the whole network to the attacker (lateral movement).

  • Vulnerabilities and penetration tests

    Periodic vulnerability scanning, prioritization by risk, and penetration tests of infrastructure, websites and applications.

  • Monitoring and incident response

    SIEM and SOC, alert rules and a rehearsed response procedure (incident response): containment, investigation, recovery and reporting.

  • Protected backup and continuity

    Immutable backup and an air-gapped copy, a BIA and a DRP that is tested in an exercise.

What we take care of, in detail

Governance, risk and compliance (GRC)

  • Outsourced CISO, support for management and the board, periodic reporting
  • Security strategy, an annual work plan and budget
  • Asset management: mapping and classifying information assets, owners, sensitivity
  • Risk management: risk assessment, risk register, treatment plan (risk treatment)
  • BIA (business impact analysis): critical processes, RTO/RPO, dependencies
  • BCP/DRP: continuity and recovery plans, exercises and tabletops
  • Organizational policies, procedures and standards
  • Compliance and regulation: the Privacy Protection Law and Amendment 13, ISO 27001, NIST CSF, the Israel National Cyber Directorate guidance
  • DPO and privacy advice, data mapping, DPAs with vendors
  • Vendor and supply chain risk management (third-party risk)
  • Preparation for audits and third-party assessments

Technical protection

  • Security architecture: Zero Trust, network hardening, web filter
  • Identity and access management (IAM), MFA, PAM, local admin, passwords
  • Hardening of Active Directory, servers, workstations and cloud
  • Vulnerability management: scans, prioritization, patch management
  • Penetration tests (PT / penetration testing): infrastructure, websites, applications, black/gray box
  • EDR / XDR, endpoint and server protection
  • Email security: SPF, DKIM, DMARC, phishing filtering
  • Cloud and SaaS security (M365, Google Workspace)
  • DLP and protection of sensitive data, encryption
  • Backup that cannot be changed (immutable) and ransomware protection
  • Secure development (secure SDLC) and code review

Monitoring and response

  • SIEM / SOC, security monitoring, alert rules
  • Cyber incident response management (IR): containment, investigation, recovery, reporting
  • Threat intelligence and leak intelligence
  • Phishing simulations and security awareness training for employees
  • Onboarding and offboarding of employees and vendors
  • A SaaS platform for managing information security in organizations (in development)

From the first conversation to an organized routine

  1. 1

    Introductory call

    What the business does, what data it holds, and which requirements have already come from customers or a regulator.

  2. 2

    Status and risk assessment

    A review of the infrastructure, the permissions, endpoint protection and backup, and a first risk register.

  3. 3

    Work plan

    A list of actions by risk and budget, separating what is handled immediately from what goes into the annual plan.

  4. 4

    Implementation and support

    Carrying out the actions, ongoing monitoring, periodic reporting to management and updating the plan when something changes.

Why the organization’s IT provider must understand security and regulation

A cyber incident in a business can start with a simple setting made without any thought about security: an open port, a shared admin account, a backup connected to the network. Whoever configures the servers, the network and the permissions effectively sets the business’s level of protection.

  1. When work stops

    Ransomware encrypts servers and workstations, and sometimes the backups connected to the network as well. Until the restore is finished there is no accounting, no access to files and no way to serve customers. How long the outage lasts (downtime) depends on what was prepared in advance, much more than on what is done on the day of the incident.

  2. When data is exposed (data breach)

    Data that leaked from a system or a compromised mailbox cannot be taken back. When it is personal data of customers, patients or employees, the exposure is also a legal event: reporting obligations (breach notification), an inquiry by the Privacy Protection Authority and complaints from the people whose data was exposed.

  3. When the regulator checks

    Amendment 13 to the Privacy Protection Law, in force since August 2025, expanded the supervision and enforcement powers of the Privacy Protection Authority, including administrative fines. In an inquiry they ask what was configured, who is responsible and where it is documented, and a verbal answer is not enough.

  4. When customers check

    Large organizations, public bodies and cyber insurers send security questionnaires and check MFA, EDR, an air-gapped backup and procedures. A supplier that does not meet the requirements loses contracts, and a business hit by an incident also loses the trust of existing customers.

  5. Where the IT provider comes in

    The settings that decide whether a breach stops at one workstation or spreads across the whole network (lateral movement) are made in day-to-day work: permissions, segmentation, updates and backup. An IT provider that knows ISO 27001, NIST CSF and the Israel National Cyber Directorate guidance builds them correctly from the start, and documents them so they hold up in an audit.

Guide: 7 questions to ask before choosing an IT provider for your business

Frequently asked questions

About information security and cyber in your organization.

Didn’t find an answer? +972-3-3801180

Many attacks are not aimed at a particular business: they scan the internet looking for an unpatched server, a weak password or a user who will click a link (phishing). A small business with customer data is a convenient target, precisely because its protection is weaker. In addition, the Privacy Protection Law and the data security regulations apply to small businesses too.

These are important components, but they cover only part of the picture. Security in an organization also includes permissions, MFA, updates, an offline backup, monitoring and a clear procedure for an incident (incident response). Without these, even good software can raise an alert about a problem without anyone handling it.

IT services make sure the systems work. Information security examines what could go wrong, what the impact on the business would be and what to do to prevent or reduce the damage (risk management). With us the two areas sit together, so protection is implemented in the infrastructure itself and does not remain a recommendation on paper.

We start with a status assessment: a review of the infrastructure, the permissions, endpoint protection, email and backup, and a vulnerability scan as needed. The result is a risk register and a list of actions by priority that can be presented to management.

Yes. Part of the work is mapping the databases (data mapping), setting the required security level, writing procedures and implementing the controls the regulations require. The goal is that at any moment you can show what was configured, who is responsible and where it is documented.

We act according to the response procedure (incident response): contain the incident, isolate what was affected, preserve evidence (forensics) and restore from a clean source. At the same time we check whether there is an obligation to report to the Privacy Protection Authority or another body, and document what was done for the investigation.

Want to know where your organization stands on information security?

Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.

Business hours: Sunday to Thursday, 08:00 to 17:00

Existing client? Open a support ticket

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch