Smart working Piergiorgio Venuti

Companies and smart working – let’s clarify

Let’s start with some clarity: smart working and teleworking are not the same thing. The second is what the British call “agile work” and means having a work contract that allows you not to have to attend company offices to work. Smart working involves a few days a week spent working remotely, typically at home.

This article deals with smart working in the general sense of a work methodology that does not involve the use of an office.

Advantages of smart working

With the rapid development of technology, employees can now work from anywhere in the world. The days when they were assigned to a desk have passed. Smart working is changing the concept of work.

Smart work starts from the assumption that “work is an activity and not a place”. Paul Allsop, founder of the Agile Organization, defines this new concept of work as follows:

Agile work consists in bringing together people, processes, connectivity, technology, time and place to find the most appropriate and effective way of working to perform a certain task. It works according to the guidelines (of the activity) but without boundaries (of how you reach it).

Once free to work remotely, employees feel emancipated, are prone to innovation and are generally more productive. Employees are more motivated and smart working leads to better customer satisfaction. Ultimately, there is a better profit for the company.

In detail

 

The definition of smart working is rather confusing. Every company, even within a specific sector, has its own way of working. There are no strict rules on how smart working is done.

There are basically four factors to consider when setting up a remote work system:

   – Time: when you work
   – Role: what do you do
   – Place: where you work
   – Sources: teams and activities

Regardless of what the smart working methods are, the company that wants to offer it, must provide adequate infrastructure to carry out remote activities.

Possible obstacles

All the evidence and data indicate that smart working works very well and offers discrete benefits for both the company and the employee. But one must be aware of the possible problems that this entails:

   – Lack of trust and responsibility
   – Corporate culture absent
   – Resistance to change
   – Difficulty in the technological approach by employees
   – Lack of responsibility and tolerance of behavioral problems

Once these problems are overcome, there will be a solid foundation on which to grow and develop a company by embracing new advantageous working methods.

Adequate company structure

In order to offer teleworking to their employees, or a smart working solution, companies must have some essential tools. Not being physically present in the office, but having to work as if they were necessary, employees must be able to take advantage of adequate infrastructure to perform their duties.

For tariff some examples:

   – Corporate laptop for employees involved in smart working
   – Cloud storage service for versatile data sharing
   – Teleconferencing tool to facilitate communication
   – Infrastructure monitoring system for data operation and control of the operation of the machines involved
   – VPN to create and manage dedicated and secure networks

Smart Working

Business tools

Companies today can count on technologies that allow them to support this work structure easily and in an economic way. By implementing virtualization solutions, relocating your human resources becomes quite simple.

The virtualization of resources can take place at different levels and offer adequate solutions for every need. There are three main ways of virtualization.

Infrastructure-as-a-Service (IaaS)

With this a model, virtualized hardware resources are made available. The company can create and manage, according to its needs, a private cloud infrastructure, without worrying about where resources are allocated.
Examples: Amazon Elastic Cloud Compute (EC2), Google Cloud Engine, Cyberfero SuperCloud.

Platform-as-a-Service (PaaS)

In this model, online platforms are offered, thanks to which the user can release the web applications and services that he intends to provide to third parties. You can develop and run your own applications through the tools provided by the provider, which guarantees the correct functioning of the underlying infrastructure.
Examples: Amazon Relational Database Service (RDS), Google Cloud SQL

Software-as-a-Service (SaaS)

This model includes applications and software accessible from any type of device, through the simple use of a client interface. In this way, the user does not have to worry about managing resources and not even the infrastructure, as they are controlled by the provider that provides them.
Examples: G Suite, Cyberfero Cloud Web Conference, Cyberfero ownCloud, etc.

Concluding

Smart working is increasingly popular and we can expect it to be the standard in the not too distant future. In order to support it, the company must have adequate services and infrastructures that support the workload.

The advantage is also guaranteed by the fact that the virtualization of resources is offered as a scalable service, capable of growing and adapting to the size of the company.

[btnsx id=”2931″]

Useful links:

ownCloud

Cloud servers

VPS Metered – Cloud location

SaaS – Software as a Service

 

Share


RSS

More Articles…

Categories …

Tags

RSS feed: Unknown Feed Unknown Feed

RSS feed: Full Disclosure Full Disclosure

  • Apache Struts2 Core Arbitrary Code Execution via OGNL Sandbox Escape November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below attempt to prevent arbitrary code execution via Object-Graph Navigation Language (OGNL) through several different mechanisms but only in a cursory fashion -- the libraries only guard against immediate calls evaluated by the OGNL engine via `SecurityMemberAccess`, but an allowed […]
  • Apache Struts2 Core TokenHelper Token Cryptographic Timing Side-Channel November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Core 7.4.0 and below performs session token comparisons cryptographically insecure early-exit comparison functions (e.g., `!=`, `memcmp`, byte-by-byte loops with `break`) that return as soon as the first mismatched byte is encountered. The execution time of the comparison is therefore proportional to the number […]
  • Apache Struts2 Spring Plugin Uses a Previously Closed Resource November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 Spring Plugin opens a Spring `ApplicationContex` via a try-with-resources block and, outside of said block, then continues to use the closed resource, resulting in an uncaught `IllegalStateException`. This particular issue prevents proper functionality and indicates poor code quality and code review standards and […]
  • Apache Struts2 Core Integer Overflow November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below fails to properly prevent integer overflows, causing wrap-arounds and other issues on a downstream forced casting into types smaller than `BigInteger`. Importantly, this finding underscores why all applications using Struts and other such platforms should perform their own input […]
  • Apache Struts2 Core Cross-Origin Protection Exemption Miskeyed to a Deployment-Wide Path November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description Apache Struts2 Core version 7.4.0 and below's `FetchMetadataInterceptor`, `CoepInterceptor`, and `CoopInterceptor` each compare their `exemptedPaths` configuration -- a per-interceptor-reference, administrator-supplied set of paths intended to exempt specific actions from the corresponding cross-origin protection -- against `HttpServletRequest.getContextPath()`. `getContextPath()` is fixed for the entire deployed web...
  • Apache Struts2 REST Plugin Fails to Properly Parse Chunked Requests November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 REST Plugin's (version 7.4.0 and below) `ContentTypeInterceptor.intercept(ActionInvocation)` only deserialises a request body and enforces the `struts.rest.content.maxLength` bound when `HttpServletRequest#getContentLength()` returns a positive value. `getContentLength()` returns `-1` whenever the `Content-Length` header is absent, which normal and appropriate for any Hypertext Transfer Protocol (HTTP)...
  • Apache Struts2 REST Plugin Untrimmed `Accept` Header Tokens Break Content Negation Fallback November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01Description The Apache Struts2 REST Plugin's `DefaultContentTypeHandlerManager.getHandlerForResponse(HttpServletRequest, HttpServletResponse)` splits the `Accept` header on commas and passes each resulting token directly to `findHandler(String)` without trimming leading or trailing whitespace. `findHandler(String)` only retries a trimmed lookup when a token contains a semicolon (`;`), so a token that merely carries […]
  • Apache Struts2 JSON Plugin Insecure Deserialisation -- Object Deserialisation Element-Count Limit Bypass November 2, 2026
    Posted by Daniel Owens via Fulldisclosure on Nov 01As of the current versions of the Apache Struts2 JSON Plugin (e.g., version 7.4.0 and the 7.5.0 snapshot dated 28 October 2026), attackers can bypass the element-count limit purported to protect Object deserialisation added to said code as part of the WW-5618 and S2-072 "hardening controls". Please […]
  • [0day-rubbish] NETGEAR RAX120 V1.2.5.18 authenticated SOAP InstallApp OS command injection to root-configured web-stack execution (6.8 Medium; conditionally 7.2 High with management exposure) October 29, 2026
    Posted by disclosure via Fulldisclosure on Oct 280day Rubbish Research Team is publicly disclosing a vulnerability in NETGEAR RAX120 (Nighthawk AX12) firmware V1.2.5.18, the WiFi 6 consumer router from NETGEAR (United States), built on the Qualcomm IPQ8074 platform. The administrative web plane of this firmware generation is a lighttpd server fronting the vendor's DNI-framework CGI […]
  • [0day-rubbish] Raritan PX3 PDU G4 firmware 4.3.14 command injection in the ping and traceroute diagnostics through an inverted hostname-validation return check (8.8) October 29, 2026
    Posted by disclosure via Fulldisclosure on Oct 280day Rubbish Research Team is publicly disclosing a vulnerability in the Raritan PX3 PDU G4, firmware version 4.3.14, the intelligent rack power distribution unit from Raritan, a Legrand company (United States). A low-privilege authenticated session converts one diagnostics request into operating-system command execution in the product's web-service context, […]

Customers