You are here: ECool IT Services |
- Fix it before broken
- Maximizes system uptime
- Improves system performance
- Improved Security
- Reduces IT costs
- Fast Priority Response
ECoolSysCare Maintenance Service
Reducing the cost and bringing you peace of mind!
At ECool we have been tring to provide the best I.T. Services to your business. Firstly it needs to be both preventative and proactive, not after problem occuring. Secondly you shouldn't have to wait hours or days to get help or have a problem resolved. Finally, the cost of the service shouldn't be as much as hiring your own I.T. staff.
ECoolSysCare Maintenance Plan
1. Hardware and networking system
| Hardware, such as computers, Network devices and peripheries inspection and audition. |  |
|---|---|
| All of the various points where physical network connection can be managed/administered. | |
| All computers, network devices and peripheries can communicate between each other efficiently and smoothly. | |
| Regulate software installation by understanding the name, functionality, vendor, and nature of the software on the system that participate in any network activities. | |
| Install all the vendors security patches and regularly do security updates of patches/vulnerabilities to the software that used in the networked environment. | |
| Thoroughly test any services that interact with the network to insure that they do not, by default, provide any unauthorized users with useful security information that could be used to attack the system. | |
| Limit users’ abilities to access sensitive information available over the network. | |
| Make and keep sufficient logs of all approved network activities. | |
| Understand all software that should be interacting with the network, the port numbers they use, the size and location of their binaries. | |
2. Software and applications
| Schedule checks with software vendors for security patches, release notes, and other relevant information to their particular configurations. | |
|---|---|
| For any software installing/installed onto the system, make sure fully aware of the credentials of the vendor, any security patches, existing exploits, and release notes that exist and check in with vendors frequently for new releases that may have bug fixes. | |
| Service Logs – Audit of server applications, service and security logs. | |
| Follow the vendor's instructions for installing software and make sure to understand the full implications of having it do so, and any side-effects created in the process. | |
| Test the configuration of the software thoroughly. | |
| The program can only be executed by authorized users, and make sure that any logs or temporary information are stored. | |
| If software runs as a daemon, make sure it properly handles buffer overflows, denial of service attacks, and general heavy system load. | |
| Be aware of all the services that are supposed to be running on the system, the typical amount of resources (e.g. CPU time, memory, disk space) that they take up. | |
| Check for unidentifiable daemons or software, or programs that are unusual in their resource consumption. | |
| Run process accounting to keep track of typical software usage patterns of the users. | |
3. Data storage and safety
| Data should be stored centrally which can be accessed conveniently by all staff and easy to do backup/recovery. | |
|---|---|
| Understand the file ownership scheme that system implements which is group based, user based, role based, or some combination of these. | |
| Know the different levels of protection that can apply to files and directories, and who has access to make changes to these protections. | |
| Know the general structure of the file system, how much is stored, where and who can typically access what parts of them. | |
| Keep logs of disk activity and any disk problems. | |
| Make sure that users are only able to access the parts of the system relevant to their setting (access right). | |
| Make sure that the file ownership schemes are consistent for various directories. | |
| Insure that users cannot have access to more disk resources than user disk quotes. | |
| Examine the security of the protocols and always check the configuration of the services to make sure that only authorized users and hosts are allowed to access shared data. | |
| Schedule secure backups of system and data to a backup media. | |
| Backup Audits – Auditing of backup applications to determine if there are any problems and confirm backups are running successfully. | |
4. Access previliage and system security
| All users should have their own accounts to access system. | |
|---|---|
| Develop a standard method for creating and maintaining user accounts. | |
| Develop clear and concise acceptable IT policies, and communicate them well to the users. | |
| Limits should be set on the amount of resources a user can consume, from number of logins to amount of disk space; make sure that the user cannot cause a security breach or take down the system out of pure stupidity. | |
| Keep accurate logs of user activity; specifically, connection time, connection duration, and the place where they logged in or connected from. | |
| Regularly check for irregular user activity; such as constantly "patrol" for failed attempts on the part of users to gain administrator privileges, access files that they shouldn't, or perform other unauthorized tasks. | |
| Verify firewall or router logs to ensure security has not been breached and logging of remote monitoring statistics. | |
Provide written reports covering maintenance activities and monitoring results. |
|
| Be aware of persons or groups who may have intentions of breaking into the system. Keep the users advised of the techniques applied and what the expectation of them to maintain security. | |
| Active Directory and Organization Unit system should be applied to control user privilege centrally based on domain level. | |
| Antivirus and Antimalware Updates – Audit of antivirus and antimalware software to ensure the latest definitions are in circulation. | |
Observe the usage patterns of the machines and users. |
| Run cracking tools regularly to check for vulnerabilities in the system configuration and manually try to break into the system through different means. | |
5. Summary and reports providing
monthly reports detailing various aspects of maintenance & monitoring work performed. |
|
|---|---|
Server storage space available at the time of the report compared against pervious months data. |
|
Current month Server Performance compared to previous months data. |
|
The status of Antivirus and Antimalware systems. |
|
Details of any updates applied to the servers. |
|
Details of the daily logging and monitoring of Backup and any action required to rectify failing backups. |
|
Guarantee
| Case Satisfied Guarantee | |
|---|---|
| Service covered period quick response | |
| High level industry standard applied | |
Support
| Work Day Phone | |
|---|---|
| Work Day Live Talk | |
| 24/7 Ticket | |
| 24/7 Email | |
| Knowledge Base | |
Summary of features
- Free quotation
- Service covered period quick response
- Case satisfied guarantee
- High level industry standard applied
-
