- Policies & Guidelines
- Is this website and service secure?
Is this website and service secure?
COMPETENCY.IO users trust us with their documents, data & ideas. That trust is based upon us keeping that data both private and secure. The information on this page is intended to provide transparency about how we protect that data. We will continue to expand and update this information as we add new security capabilities and make security improvements to our products.
Security is extremely important within COMPETENCY.IO. Our security charter is about protecting the data you store in our service. We drive a security program that includes the following focus areas: product security, infrastructure controls (physical and logical), policies, employee awareness, intrusion detection, and assessment activities.
Our Technical Team runs an in-house Incident Response program and provides guidance to employees on how to report suspicious activity. Our team has procedures and tools in place to respond to security issues and continues to evaluate new technologies to improve our ability to detect attacks against our infrastructure, service, and employees.
We periodically assess our infrastructure and applications for vulnerabilities and remediate those that could impact the security of customer data. Our Technical Team continually evaluates new tools to increase the coverage and depth of these assessments.
We define our network boundaries using a combination of load balancers, firewalls, and VPNs. We use these to control which services we expose to the Internet and to segment our production network from the rest of our computing infrastructure. We limit who has access to our production infrastructure based on business need and strongly authenticate that access.
We protect our service against distributed denial of service (DDoS) attacks using an on-demand mitigation service.
We never store your password in plaintext. When we need to securely store your account password to authenticate you, we use PBKDF2 (Password Based Key Derivation Function 2) with a unique salt for each credential. We select the number of hashing iterations in a way that strikes a balance between user experience and password cracking complexity.
We limit failed login attempts on both a per-account and per-IP-address basis to slow down password guessing attacks.
Securing our Internet-facing web service is critically important to protecting your data. Our Technical Team constantly assesses our service for common application security issues including: CSRF, injection attacks (XSS, SQLi), session management, URL redirection, and clickjacking.
Our service is multi-tenant and does not segment your data from other users’ data. Your data may live on the same servers as another user’s data. We consider your data private and do not permit another user to access it unless you explicitly share it.
We retain your content unless you take explicit steps to delete it. Deactivating a personal account or revoking access to a business account does not automatically remove content.
Customer Account Access
Like most cloud services, we have an administrative tool. This tool allows our customer service and platform administration teams to resolve customer issues. We limit who has access to customer data within this administration tool based on business need and strongly authenticate that access.
We periodically review employee access to customer accounts to identify administrative abuse and minimize the situations where we might need to access account content in the future.
Our service performs server-side logging of client interactions with our services. This includes web server access logging, as well as activity logging for actions taken through our API. These logs also include successful and unsuccessful login events. Due to the nature of our client / server architecture, we cannot reliably know whether data was viewed.