At Quality NOC we have a Service Desk product to follow up your tickets, escalate, contact your engineers (email, sms or Phone), solve incidents based on your custom procedure manual, close tickets or create new ones.
Ticket handling: We can adjust to your SLA agreements, for example:
React: immediately after receiving an SMS alarm, ticket or call.
The ticket will be handle within 30 min max. First contact: email or call, within 1 hour.
Updates: Hourly, or as agreed between customer and Quality NOC.
Quality NOC shall specify the log time elapsed in a convenient format.
We have 2 Options:
24/7: Running service from 00:00 to 23:59 everyday
Off-Business hours: Monday to Friday (08:00 to 16:00) and Saturday, Sunday and Holidays (24 hrs).
Both options can be delivered with a fixed monthly price.
Please contact us to find out more and we send you a quotation.
Quality NOC – Network Operations Center
Quality NOC S.L., provides remote monitoring and management 24/7 Network Operations Center (NOC) that enables monitor, troubleshoot and maintain IT environments.
Our technicians take on the burden of supporting your customers, freeing up your time for other tasks. This allows you and your team to focus on sales, marketing, and building your company while we work hand in hand with your clients. All of our technicians are trained Windows and Linux Experts and we’re capable of handling simple issues and all the way up to some of the most difficult tasks.
We can use any system you are working with, and as soon as we get the ticket, we react.
This way we contact (email or call) your engineers based on the contact and escalation matrix.
We can replay the ticket, forward or contact to the engineer, do a followup and send updates to the customer based on your SLA.
We will also do escalations if needed and we can prepare a monthly report about the incidents.
We are ready to take your tickets and we speak English, Spanish, Norwegian/Swedish and Portuguese. We are planning to add German soon too.
We can offer you a fixed monthly price based on monthly number of tickets you receive. This is a great solution for your company.
The similarities between the role of the Network Operation Center (NOC) and Security Operation Center (SOC) often lead to the mistaken idea that one can easily handle the other’s duties. Furthermore, once a company’s security information and event management system is in place, it can seem pointless to spend money on a SOC. So why can’t the NOC just handle both functions? Why should each work separately but in conjunction with one another? Let’s take a look a few reasons below.
First, their roles are subtly but fundamentally different. While it’s certainly true that both groups are responsible for identifying, investigating, prioritising and escalating/resolving issues, the types of issues and the impact they have are considerably different. Specifically, the NOC is responsible for handling incidents that affect performance or availability while the SOC handles those incidents that affect the security of information assets. The goal of each is to manage risk, however, the way they accomplish this goal is markedly different.
The NOC’s job is to meet service level agreements (SLAs) and manage incidents in a way that reduces downtime – in other words, a focus on availability and performance. The SOC is measured on their ability to protect intellectual property and sensitive customer data – a focus on security. While both of these things are critically important to the success of an organisation, having one handle the other’s duties can spell disaster, mainly because their approaches are so different.
Another reason the NOC and SOC should not be combined is because the skillset required for members of each group is vastly different. A NOC analyst must be proficient in network, application and systems engineering, while SOC analysts require security engineering skills. Furthermore, the very nature of the adversaries that each group battles differs, with the SOC focusing on “intelligent adversaries” and the NOC dealing with naturally occurring system events. These completely different directions result in contrasting solutions which can be extremely difficult for each group to adapt to.
Lastly, the turnover rate in a SOC is much higher than that of a NOC. Perhaps it’s the very nature of the role, but the average employment time for a level 1 SOC analyst is around 2 years or less. Tenure of a NOC analyst is much longer. It only stands to reason, then, that asking a NOC analyst to handle their own duties and also take on those of SOC will likely result in a much higher attrition rate overall.
The best solution is to respect the subtle yet fundamental differences between these two groups and leverage a quality automation product to link the two, allowing them to collaborate for optimum results. The ideal system is one where the NOC has access to the SIEM, so they can work in close collaboration with the SOC and each can complement the other’s duties. The SOC identifies and analyses issues, then recommends fixes to the NOC, who analyses the impact those fixes will have on the organisation and then modifies and implements accordingly.