Frequently asked questions Page 4 of 10

Frequently asked questions — page 4

• What is the difference between Structured Cabling and point-to-point cabling for moves, adds and changes?

  Structured Cabling centralises connections in planned spaces (such as TR/TE and distribution areas), making MACs faster and safer. Point-to-point links are harder to rework and often increase downtime when devices move or requirements change.
• How do Structured Cabling standards like ANSI/TIA-568 and ISO/IEC 11801 affect equipment compatibility and predictable performance?

  These standards define design rules and performance targets so installed links behave consistently across vendors and use cases. In practice, “standards-compliant” means the system is built and tested to meet the expected transmission characteristics.
• Which media is typically used for Structured Cabling: twisted pair, multimode fibre, or single-mode fibre?

  Twisted pair is commonly used for horizontal links to work areas, while fibre is selected for longer distances, higher capacity needs or future growth. Multimode and single-mode fibre are chosen based on reach, performance requirements and network design.
• How does the main distribution area support MAC activities compared with running long patch cords to hardware?

  A main distribution area (and related distribution points) keeps patching and cross-connections organised and controlled. This reduces the need for ad-hoc cabling changes and makes troubleshooting and reconfiguration more repeatable.
• What are the key constraints for horizontal cabling length, and what could reduce allowable lengths?

  Horizontal cabling has design limits to ensure performance across the channel. Allowable lengths can be reduced by factors such as consolidation points or additional link elements, so scoping should account for the full channel composition.
• What’s the difference between a VoIP business phone system and a SIP trunk service?

  A VoIP business phone system typically includes call handling features like extensions, voicemail, routing, and admin tools. A SIP trunk service mainly provides the connection to your phone numbers, often requiring separate PBX/telephony software.
• Which pricing model is better for small teams: per-user plans or pay-as-you-go per number/minute?

  Per-user plans are usually better when headcount is stable and you want predictable monthly costs with bundled features. Pay-as-you-go can be better when call volume varies or you need flexibility for scaling and international traffic.
• Do business VoIP systems support number portability and international calling?

  Many business VoIP providers support number portability and offer international calling options, but availability and pricing vary by region. Confirm portability rules, supported countries, and any per-minute or routing charges.
• What business features should I prioritise: IVR, call queues, voicemail transcription, or video meetings?

  Prioritise based on your call flows: IVR and queues for structured inbound handling, voicemail transcription for faster follow-up, and video meetings if you rely on remote collaboration. Ensure the provider supports the exact workflows you need.
• How do I evaluate reliability and security (e.g., MFA, encryption) before switching my phone system?

  Ask about authentication controls like MFA, encryption options, and how they protect signalling and media. Also review uptime approach, support SLAs, monitoring/alerts, and how the system behaves during network issues.
• How often should you schedule preventive IT maintenance for PCs and servers?

  As a baseline, it’s often sensible to schedule a quarterly or semi-annual review depending on criticality. Higher-impact systems require more frequent attention and ongoing monitoring.
• Does preventive maintenance include software updates, security patches and backups?

  Yes. A serious preventive plan includes software updates, applying patches, reviewing antivirus and verifying backups to ensure recoverability.
• What’s the difference between preventive and corrective maintenance in day-to-day practice?

  Preventive maintenance acts before a failure, with scheduled reviews and optimisation. Corrective maintenance is carried out once an incident has occurred, with the goal of restoring service.
• Is preventive maintenance carried out for WiFi networks and equipment such as printers and peripherals?

  Yes. The health of the network is reviewed (coverage, configuration and performance), and peripherals such as printers are also checked to prevent jams, driver failures and connectivity issues.
• How do you measure the reduction in incidents and time saved after rolling out the plan?

  You measure it with KPIs such as the number of incidents, mean time to recovery, downtime and lost hours. After the first actions, you compare results against the baseline.
• What does a “full network threat management” strategy include beyond vulnerability scanning?

  It includes a full lifecycle: asset visibility, network security controls, monitoring/telemetry, detection, coordinated response and recovery. Scanning is only one part of reducing exploitation windows.
• How are vulnerabilities prioritised so the team addresses what’s most critical to the business first?

  They’re prioritised by risk, combining asset criticality, network exposure, the likelihood of exploitation and potential business impact. The goal is to tackle first what reduces impact and exposure time the most.
• How do network monitoring (NOC) and security operations (SOC) work together in a unified approach?

  The NOC provides observability and availability, while the SOC focuses on security, detection and investigation. In a unified approach, both teams share context and data to speed up response decisions.
• How do reports and metrics help demonstrate regulatory compliance and the programme’s effectiveness?

  Reports turn operational activity into evidence: asset coverage, remediation status, detection and response times, and change traceability. This makes audits easier and improves decision-making.
• What role do automation and data integration play in improving detection and response?

  Automation reduces time and errors by orchestrating actions (for example, containment or alert enrichment). Data integration enables correlation between vulnerabilities, traffic and security events.
• How do I choose the right preventive maintenance frequency for laptops, servers, and network equipment?

  Start by assessing asset criticality and failure history, then map tasks to time- and usage-based triggers. Validate the frequency with evidence (health checks, error rates, and incident trends) and adjust it periodically to avoid over-maintenance.
• What should be included in an IT preventive maintenance checklist for security patching and malware scanning?

  Include OS and application patching, antivirus/EDR configuration checks, malware scans, and verification that updates completed successfully. Also review security baselines (accounts, unused profiles, and hardening settings) and confirm logs are clean.
• Can preventive IT maintenance be implemented for remote teams with limited access to devices?

  Yes. Use remote-friendly tasks such as patch management, configuration audits, backup integrity verification, and health telemetry checks. For physical-only items, schedule periodic on-site access or partner support where required.
• What metrics best demonstrate ROI from preventive IT maintenance?

  Track downtime reduction, incident frequency and severity, mean time to recover, repair costs avoided, and lifespan extension indicators (e.g., disk health trends). Pair this with service-level performance and stakeholder reporting.
• When should we move from time-based maintenance to condition-based or predictive approaches in IT?

  Move when you have reliable telemetry (disk SMART, event logs, and network error counters) and enough historical data to correlate signals with failures. Start with condition-based triggers for high-risk assets, then expand to predictive recommendations.
• What is included in IT maintenance for businesses in Valdemoro?

  Includes remote and on-site support for incidents, preventive maintenance to reduce failures, and security reviews. It also integrates backup and recovery management to maintain continuity.
• Do you offer an initial audit or assessment before we sign up?

  Yes. We carry out an audit and an inventory of your IT environment to understand the status of your equipment, servers, communications, and security measures. Based on that information, we tailor the plan to your operations.
• Is support provided on-site, remotely and by phone, and what are the hours?

  Support is provided via phone, remotely and, when necessary, with on-site assistance. The service runs during working hours from Monday to Friday, with response times defined according to the incident type.
• Does it include security monitoring and backup management?

  The maintenance includes endpoint security and protection measures, as well as backups and recovery criteria. The aim is to reduce risk and avoid prolonged downtime.
• Can you adapt the plan if we have critical systems or minimal disruption requirements?

  Yes. We define a model based on criticality, tolerance for downtime, and the type of systems. For sensitive environments, we prioritise continuity, planned recovery, and preventive maintenance with lower impact.
• What makes network threat management “comprehensive” compared with basic antivirus or perimeter-only security?

  Comprehensive network threat management covers the full lifecycle (identify, protect, detect, respond, recover) and focuses on threat behaviour across network segments. It combines visibility, detection signals, and response workflows rather than relying only on endpoint malware prevention or perimeter controls.
• How do UTM, MDR, and XDR differ for covering detect and respond across networks?

  UTM typically bundles network security controls for prevention and some detection. MDR adds managed detection and response capabilities for investigation and containment. XDR expands detection and correlation across multiple telemetry sources (network, endpoint, identity, cloud) to improve prioritisation and response consistency.
• Which NIST CSF functions should we prioritise first for a network-focused threat programme?

  Start with Identify and Protect to reduce blind spots and enforce consistent network policies. Then strengthen Detect and Respond with monitoring coverage, alert triage, and incident playbooks. Finally, validate Recover with recovery checks and lessons learned.
• How can threat intelligence improve detection of unknown or evolving threats in our network?

  Threat intelligence provides context for indicators, behaviours, and emerging TTPs, improving how alerts are prioritised and how detections are tuned. It helps teams recognise abnormal patterns sooner and reduces time spent on low-value alerts.
• What should we look for to reduce security tool fragmentation and get unified visibility across networks, endpoints, and clouds?

  Look for data unification capabilities, consistent event normalisation, and correlation across telemetry sources. Also assess how well your tools support shared incident workflows, common KPIs, and automated enrichment for faster triage.
• What is the difference between network management and network monitoring in a business?

  Monitoring focuses on detecting and measuring (alerts, metrics, logs). Network management also includes operating the environment, maintaining it, applying controlled changes, ensuring configuration, managing security, and ensuring continuity.
• What tasks should an IT managed service (MSP) for network management cover?

  Typically, it includes preventive maintenance, monitoring, change management, updates, technical support, incident response, and coordination of security and continuity with defined SLAs.
• How do I choose a monitoring solution that can scale with my infrastructure?

  Assess scalability, integration (APIs and connectors), alert management (policies and noise suppression), compatibility with virtualised environments and containers, and correlation capabilities for troubleshooting.
• What should I require from alert management to reduce response times?

  Escalation channels and owners by alert type, severity policies, escalation rules, adjustable thresholds, and end-to-end incident lifecycle traceability (detection, diagnosis, and closure).
• Does network management include incident recovery plans?

  It should include resilience and recovery: procedures, tests, coordination with backups, and restoration verification. It’s not enough to “have backups” — you need to prove that they work.
• What services are included in IT Maintenance in Valdemoro (support, networks, hardware/software updates)?

  Typically it includes Service Desk support, 1st level incident resolution, network and cabling maintenance, hardware/software updates, and system inventory. The exact scope is defined after an initial audit of your devices and environment.
• How do you handle incidents and service requests through a ticketing/Service Desk process?

  Requests are logged as tickets, prioritised, and handled with a clear workflow for diagnosis and resolution. You receive resolution reporting, and issues are reviewed proactively to reduce repeat incidents.
• Do you provide 1st level repairs and when do you escalate to specialist technicians?

  Yes—1st level support covers common incidents and first diagnostics. If the issue requires deeper expertise (network, security, infrastructure), it is escalated to the relevant specialist team.
• Can you support preventive maintenance to reduce unplanned downtime and repair costs?

  Yes. Preventive maintenance focuses on keeping systems healthy through monitoring, updates, backup checks, and security reviews. This reduces unplanned downtime and helps avoid costly repairs.
• Do you include network security and cybersecurity checks as part of ongoing maintenance?

  Yes. Security-by-design is part of ongoing maintenance, including security software configuration, access settings for internet and email, and cybersecurity checks aligned with your requirements and standards.
• What does an IT network management service typically include for a business?

  It usually covers monitoring and fault management, configuration and provisioning, security operations, and performance measurement. Many services also include maintenance, controlled change workflows, and reporting for business stakeholders.
• How quickly can network management teams detect and resolve faults to reduce downtime?

  Detection speed depends on telemetry coverage and alert quality, while resolution speed depends on runbooks, escalation paths, and safe change processes. A good service prioritises faults by business impact and uses structured troubleshooting.
• Do I need a NOC or managed services, or can my internal IT team handle network management?

  If your internal team lacks 24/7 coverage, monitoring depth, or security operations capacity, a NOC or managed services model can fill the gap. The decision should be based on workload, skills, and the required service levels.
• What are the first network metrics and alerts we should implement for reliable performance and visibility?

  Start with availability, latency, packet loss, interface utilisation, and error rates, then add security-relevant signals such as intrusion events and suspicious access patterns. Define baselines and thresholds that match your business services.
• How does network management support hybrid and remote work environments securely?

  It ensures secure remote access (e.g., VPN and encryption), consistent policy enforcement, and monitoring of connectivity and endpoint risk. It also supports reliable branch and cloud connectivity with controlled change and segmentation.
• What’s the difference between IT network security and cybersecurity?

  IT network security focuses on protecting networks and communications (traffic, segmentation, access, and endpoints). Cybersecurity is broader and includes applications, identity, processes, and incident response.
• What’s the priority solution for blocking unauthorised traffic: a firewall or NAC?

  A firewall controls permitted traffic between zones and reduces exposure. NAC limits which devices and users can connect and with what permissions, so it typically complements a firewall to prevent unauthorised access.
• Do I need a VPN if I already have a firewall and access controls?

  A VPN provides a secured, encrypted and authenticated channel for remote access, especially when users connect from untrusted networks. Firewalls and access controls help, but they don’t replace tunnelling encryption and authentication.
• How does network segmentation help reduce the risk of intrusion?

  Segmentation limits lateral movement and reduces an attacker’s reach if they compromise a device. It also makes it easier to apply different policies per zone based on criticality.
• What practices should I follow to maintain network security in the long term?

  Prioritise patch management, regular audits, log review, security testing where applicable, and an incident response plan. Complement this with backups and recovery to minimise impact.
• What’s the difference between preventive and corrective maintenance for network infrastructure?

  Preventive maintenance aims to prevent failures through scheduled reviews, patches, and security controls. Corrective maintenance happens when an issue occurs—diagnosing it and repairing or replacing the affected components.
• Does it include security auditing and patch management?

  A complete plan typically includes reviewing policies, hardening, checking firewalls/IPS, and updating firmware and software. The goal is to reduce vulnerabilities and minimise operational risk.
• Is performance monitoring with alerts for latency and bandwidth included?

  Yes, monitoring allows us to detect bottlenecks and degradation before they affect users or applications. Thresholds and alerts are defined to act quickly.
• What service levels and response times are covered for network maintenance?

  It depends on the contract and how critical it is: coverage can be offered by time slots, with priority response and escalation. The key is to ensure the SLA matches the impact of each site or system.
• Does maintenance include hardware support out of warranty, and is there a guarantee of resolution on first attempt?

  Some suppliers cover hardware support out of warranty and set resolution commitments. It’s worth reviewing the scope, replacement conditions and the technical escalation process.
• What network security controls should we prioritise first for an enterprise environment?

  Start with identity and access controls, then enforce segmentation and least privilege. Next, deploy firewall policy enforcement and intrusion detection, and ensure central logging for visibility.
• How does Zero Trust Network Access (ZTNA) differ from traditional perimeter security?

  Perimeter security assumes trusted internal networks, while ZTNA continuously verifies user and device context before granting access. This reduces lateral movement when credentials or sessions are compromised.
• What should we measure to prove network security effectiveness?

  Track outcomes aligned to confidentiality, integrity, and availability: blocked malicious traffic, detection coverage, mean time to detect and contain, and audit evidence for policy compliance.
• Which security controls are most important for remote users and distributed locations?

  Use secure remote access (such as VPN-style encrypted connectivity), strong authentication, and consistent endpoint protections. Pair this with segmentation and monitoring so remote access cannot bypass core controls.
• How can AI and analytics support faster detection and response in network security operations?

  Analytics can prioritise alerts by correlating telemetry and highlighting anomalies, reducing noise for analysts. This supports faster triage and more consistent incident response workflows.
• What does network infrastructure maintenance typically cover in practice?

  It usually covers monitoring and verification of network devices, structured cabling and fibre maintainability, Wi‑Fi performance checks, firewall/VPN posture, and routine configuration hygiene. Many programmes also include reporting and incident response workflows.
• How often should we perform network maintenance to reduce outages and security risks?

  A common approach is daily monitoring, weekly verification of access and alerts, and monthly deeper checks such as firewall rule review and connectivity/performance testing. The exact cadence depends on risk, change frequency, and device criticality.
• Can we maintain network performance without disrupting business operations?

  Yes, when maintenance is planned with maintenance windows, low-impact testing, and clear change control. Proactive checks and evidence-based troubleshooting reduce the need for disruptive interventions.
• What should we look for when choosing an external network maintenance partner?

  Look for end-to-end monitoring/reporting, defined maintenance windows, rapid response processes, documentation standards, and security evidence handling. Confirm coverage for both network and cabling maintainability, plus how they manage changes and handovers.
• Do you provide monitoring and reporting as part of network maintenance services?

  In a managed model, monitoring and reporting are typically central, supported by proactive oversight and rapid response governed by service-level governance. Ask for what is measured, how often reports are delivered, and what actions are triggered by alerts.
• What are the steps to install a cloud-based phone system from scratch?

  It starts with account setup and service activation, followed by defining numbers and extensions in the panel. Then, ring groups, auto attendant, and voicemail configurations are set up, and validated with tests before going live.
• What information do I need before switching on the phone system?

  You need business details, a numbering plan (internal numbers and extensions), call flows (call forwarding, operator, schedules) and network requirements. Based on that, the initial configuration is prepared and time-to-launch is reduced.
• Can I integrate the phone system with my CRM and email?

  Yes, in many cases you can integrate notifications and automations (for example, call logging or email sending). Feasibility depends on the phone system model and the customer’s ecosystem, so it’s worth confirming this before installation.
• How do you ensure call quality before full deployment?

  We conduct internal and external call tests, verify ringing and transfers, and check voice quality according to the network. We also validate behaviour during real usage hours and scenarios.
• What security and privacy measures should I require during installation?

  Exige role-based access control, encryption where applicable, password policies and network segmentation if relevant. Also request information on compliance and data processing under the applicable framework.
• What does IT Support Madrid for companies exactly include?

  It includes incident management and user assistance, preventive maintenance, and support for infrastructure (systems and networks). Additionally, it usually includes security, backups and protection configuration depending on the environment.
• How do you handle incidents, and what process do you follow once a problem is reported?

  We log the ticket, classify it by impact and urgency, carry out diagnosis (usually remotely) and, if needed, escalate or intervene on site. Closure includes evidence, corrective actions and preventive recommendations.
• Do you offer IT security support within maintenance?

  Yes. The support includes security configuration and review, protection against threats and best practices. It also integrates continuity through backups and access control.
• Do you work with companies of any size, or only with certain profiles?

  The service adapts to the size of your fleet and the complexity of the environment. It’s common for SMEs and also for organisations with more specific needs, adjusting the delivery model and coverage.
• How can I request an assessment or talk to the IT support team?

  You request an assessment of the case to review the status of the environment, define scope, and propose a delivery model. Based on that information, operational timelines, the service process and service conditions are agreed.
• Do you offer installation and also maintenance for IT networks?

  Yes. We can carry out the installation project and, if needed, include maintenance and support to prevent incidents, fix issues, and manage expansions.
• Do you carry out a needs assessment and review actual network usage beforehand?

  We start with a consultation and requirements analysis to understand usage, inventory, and performance targets. Based on that, the infrastructure is designed.
• Can you implement structured cabling and wireless networks in the same project?

  Yes. We can integrate structured cabling and, where applicable, enterprise Wi‑Fi networks so they coexist with a maintainable wired infrastructure.
• How do you guarantee network security?

  We apply best practices such as segmentation, access control, and protection criteria. Security is designed from the start and validated during deployment.
• What criteria should I use to choose an IT networking company?

  Review scope, phases, deliverables (documentation and testing), experience with cabling/certification, the security approach, and the maintenance and support plan.
• What components are typically included in switchboard installation?

  A typical switchboard includes a main switch (or incomer), circuit breakers, RCD/GFCI protection where required, neutral and earth (N/PE) buses, terminal blocks, and measuring/auxiliary devices where specified. The exact mix depends on the consumer groups and protection strategy.
• How do I calculate how many modules my switchboard will need?

  Start by listing each device per circuit (breakers, RCDs, isolators, relays, spares) and convert their sizes into module units (commonly 17.5 mm per module). Add a practical spare margin for future expansion and for termination/space constraints.
• Should I use a line diagram or a group diagram to make fault finding easier?

  A line diagram can make it easier to isolate an entire line, while a group diagram can simplify grouping by function. Choose based on how you expect faults to be reported and how quickly you need to isolate affected consumers.
• What should I check after wiring but before switching the panel on?

  Carry out continuity checks, insulation resistance tests, and verify polarity/phase identification. Also confirm correct bus connections (N/PE), that terminations are secure, and that protective devices are correctly installed and labelled.
• How do I choose a switchboard enclosure and verify the manufacturer’s documentation?

  Select an enclosure that matches your module count with spare capacity and supports safe cable routing and ventilation. Verify the manufacturer’s documentation, such as certificates/passports, operating rules, and compatibility information for the installed devices.
• What is the difference between remote IT support and on-site IT support in Madrid?

  Remote support resolves most software and configuration issues quickly, while on-site support is used for hardware, physical access, or complex deployments. A good provider coordinates both based on urgency and impact.
• Which devices and operating systems do you support (Windows, macOS, and business hardware)?

  You should confirm endpoint coverage for Windows and macOS, as well as the typical business hardware you use (for example, laptops and standard peripherals). Ask how onboarding and configuration are handled for new devices.
• Do you manage Google Workspace and also support collaboration tools like Zoom?

  Many IT support services cover Google Workspace administration and user support, plus troubleshooting for Zoom and meeting workflows. Confirm what’s included (accounts, permissions, meeting-room readiness, and user guidance).
• How do ticketing and escalation work for urgent incidents?

  Providers should use a ticketing process with clear priority levels and escalation paths. Ask what response times apply to urgent issues and who is responsible for escalation.
• What should I ask for to compare SLAs between IT support providers?

  Request SLA details by priority: expected response times, resolution/handling targets, communication frequency, and reporting. Also ask how monitoring and preventive maintenance are included.
• How do you start a network project—assessment or discovery first?

  Most Computer Network Company engagements begin with discovery: inventory, requirements, current performance, and risk review. This creates a baseline and success criteria before design and implementation.
• What’s included in managed network services?

  Managed services typically cover monitoring, support, preventive maintenance, patching coordination, and incident handling. You should also receive reporting and clear escalation paths.
• Can a network partner handle VPN, wireless, and cloud migrations together?

  Yes, if the provider scopes the work end to end and aligns security controls across on-prem and cloud. The key is a unified design, a testing plan, and operational handover.
• What security deliverables should I expect from a secure networking provider?

  Look for defence-in-depth deliverables: firewall and filtering policies, secure remote access (VPN), vulnerability and patch management, and ongoing threat monitoring with documented procedures.
• How are network consulting and implementation projects priced?

  Pricing is often split between fixed-scope implementation (design, build, testing) and ongoing managed support (retainer). The best providers define scope boundaries and SLAs clearly.