Security Assessment and Disaster Recovery
We work closely with all levels of your organization to ensure that your WebTA installation adheres to Federal security guidelines such as NIST 800-115, NIST 800-53 and NIST 800-37. A Security Assessment covers a full range of factors, from physical security (access to the server room/hardware, for example), to network-level security (remote administrative logins, for instance) and susceptibility to web hacks (cross-site scripting and SQL-injection, e.g.). If you have a distributed installation, as many organizations do, all physical and virtual elements will be involved in the assessment.
Security assurance does not end with the successful conclusion of a security assessment. Because the physical and software characteristics can change over time – through network upgrades or new software versions – rechecking the security of your WebTA installation is important. Using state-of-the-art tools, Linear B conducts vulnerability scans to help you maintain a secure WebTA environment after any software or hardware configuration change.
Even with top-notch security controls in place, there is one type of issue that can arise at any time: Disaster. Floods, fires, earthquakes are just a few examples of disasters that can overwhelm or even wipe out the software service you use every day. Since WebTA is usually the primary software product used for ensuring payroll and leave are handled on time and accurately, a good disaster recovery plan is essential.
There are many options available for handling the disaster, ranging from using a temporary, limited-functionality server to a full-functioning automatic switch-over service. The appropriate level of disaster recovery you implement will vary according to your organization’s mandates, regulations, and budget.
We can help you design a cost-effective cloud-based WebTA Disaster Recovery option that will meet your organization’s requirements. If your organization requires its own disaster recovery site, we can help you determine how much capacity you will need to run all mission-critical services. Capacity recommendations include amount of disk storage to handle the supporting data as well as server sizing to run applications and backend services. A disaster recovery plan also takes into account methods for managing user authentication, Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP), overall monitoring, and alert systems.
Remember that it is important to test a Disaster Recovery plan before a disaster happens! Scheduling a simulated disaster is the best way to evaluate how well your plan will perform when a true disastrous event occurs. Contact us to find out how Linear B can help you meet your security and disaster preparedness requirements.