Hostilla.pl FAQ

Security, malware, backups, GDPR and NIS2

Imunify360, CXS, malware, backups, CSF/LFD, geo-blocking, GDPR, NIS2 and continuity. Answers are based on Hostilla.pl hosting services, cPanel and eTOP infrastructure.

27 questions in this topic

Expand a question to see the answer. The content is visible in HTML and can be indexed by search engines.

351. How does Imunify360 work?

For the topic "how does Imunify360 work" first check the setting in security layers, backups and ticket with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

352. How do exploit scanners work?

For the topic "how exploit scanners work", first check the setting in security layers, backups and report with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

353. How does CXS work?

For the topic "how CXS works" first check the setting in security layers, backups and ticket with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

354. How do our own malware signatures work?

For the topic "how our own malware signatures work", first check the setting in security layers, backups and report with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

355. How many times a day do we update signatures?

For the topic "how many times a day do we update signatures", first check the setting in security layers, backups and the report with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

356. What is worth knowing about the malware lab?

For the topic "what is worth knowing about a malware lab", first check the settings in security layers, backups and reports with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

357. How do we block traffic from dangerous domains?

For the topic "how we block traffic from dangerous domains", first check the settings in security layers, backups and reports with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

358. How does the client check detected files?

For the topic "how the client checks detected files", first check the setting in security layers, backups and the report with specific traces.

Hostilla uses multiple layers of security: Imunify360, exploit scanners, CXS, its own malware signatures updated several times a day, email protection and blocking traffic from dangerous domains.

The client should know that detecting a suspicious file does not always mean the end of the job. You need to remove the cause of the infection, update the application and change passwords.

359. What to do if a website is infected?

For the topic "what to do if a website is infected", first check the setting in security layers, backups and the report with specific traces.

After a website infection, spam sending or mailbox hijacking, you need to act quickly: change passwords, check CMS users, FTP, e-mail, crons, redirects and outdated plugins. Simply deleting one file often does not fix the source of the problem.

In your report, please include the domain, symptoms, time of detection, sample messages or files, and recent changes to the application.

360. What to do if your account is blocked after an infection?

For the topic "what to do if your account is blocked after an infection", first check the setting in security layers, backups and the report with specific traces.

After a website infection, spam sending or mailbox hijacking, you need to act quickly: change passwords, check CMS users, FTP, e-mail, crons, redirects and outdated plugins. Simply deleting one file often does not fix the source of the problem.

In your report, please include the domain, symptoms, time of detection, sample messages or files, and recent changes to the application.

361. What to do when an account sends spam?

For the topic "what to do when an account sends spam", first check the setting in security layers, backups and report with specific traces.

After a website infection, spam sending or mailbox hijacking, you need to act quickly: change passwords, check CMS users, FTP, e-mail, crons, redirects and outdated plugins. Simply deleting one file often does not fix the source of the problem.

In your report, please include the domain, symptoms, time of detection, sample messages or files, and recent changes to the application.

362. What to do if the mailbox has been taken over?

For the topic "what to do if the mailbox has been compromised", first check the setting in security layers, backups and the report with specific traces.

After a website infection, spam sending or mailbox hijacking, you need to act quickly: change passwords, check CMS users, FTP, e-mail, crons, redirects and outdated plugins. Simply deleting one file often does not fix the source of the problem.

In your report, please include the domain, symptoms, time of detection, sample messages or files, and recent changes to the application.

363. How to change passwords after an incident?

For the topic "how to change passwords after an incident", first check the setting in security layers, backups and the report with specific traces.

After a website infection, spam sending or mailbox hijacking, you need to act quickly: change passwords, check CMS users, FTP, e-mail, crons, redirects and outdated plugins. Simply deleting one file often does not fix the source of the problem.

In your report, please include the domain, symptoms, time of detection, sample messages or files, and recent changes to the application.

364. How to restore a page from a backup?

For the topic "how to restore a website from a backup", first check the settings in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

365. How much backup does each account have?

For the topic "what backup does each account have", first check the setting in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

366. How often do we make backups?

For the topic "how often do we make backups", first check the setting in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

367. How long do we keep backups?

For the topic "how long do we keep backups", first check the setting in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

368. What does backup include: files, databases, email?

For the topic "what includes backup: files, databases, email" first check the setting in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

369. How to restore a single file?

For the topic "how to restore a single file", first check the setting in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

370. How to restore the database?

For the topic "how to restore the database", first check the settings in security layers, backups and the report with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

371. How to restore email?

For the topic "how to restore email", first check the settings in security layers, backups and the ticket with specific traces.

The backup may include files, databases and email, depending on the service and available backup point. When restoring, specify exactly what is to be restored: file, directory, database, mailbox or the entire account.

372. What is worth knowing about GDPR in hosting?

For the topic "what is worth knowing about GDPR in hosting", first check the settings in security layers, backups and notification with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.

373. What is worth knowing about NIS2 in hosting?

For the topic "what is worth knowing about NIS2 in hosting", first check the setting in security layers, backups and the report with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.

374. What is worth knowing about eTOP/DataHouse organizational compliance?

For the topic "what is worth knowing about eTOP/DataHouse organizational compliance", first check the setting in security layers, backups and notification with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.

375. What is worth knowing about ISO and procedures?

For the topic "what is worth knowing about ISO and procedures", first check the setting in security layers, backups and notification with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.

376. What is worth knowing about the DataHouse data center?

For the topic "what is worth knowing about the DataHouse data center", first check the setting in security layers, backups and the report with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.

377. What is worth knowing about AS20853 and infrastructure?

For the topic "what is worth knowing about AS20853 and infrastructure", first check the setting in security layers, backups and the report with specific traces.

We describe GDPR and NIS2 as the organizational and procedural layer of hosting. It is worth indicating the roles of the administrator and processor, entrustment agreements, security procedures, DataHouse data center, ISO and the AS20853 network.

We do not make promises without documentation.