By providing you access to our all security and privacy practices on this pages and on our Trust Center, we think you have all the information necessary to choose, if yasoon apps are a good fit for your company.
To make it even easier for you, we have collected several Q&As on this page for you to browse.
If you still cannot find what you’re looking for, please contact our support team with the missing question and the purchase you want to make.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Customer Access Requirements/Questions for Login/Account management
Are all identified security, contractual, and regulatory requirements for customer access contractually addressed and remediated prior to granting customers access to data, assets, and information systems?
Not applicable. We do not provide our own user accounts and do not target specific regulatory industries.
Does the system to purchase support MFA enforcement?
We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
Does the system to purchase support SSO e.g. OKTA ?
If configured in Atlassian or Microsoft. In general not really applicable: We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
Does the system to purchase support setting custom complex password policy ?
In general not really applicable: We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
...
Yes
How is access to the VPN authenticated?
User name and password + second factor (e.g. token).
Is it possible for devices that are not owned and managed by your company to connect to your internal network remotely through VPN?
No, this is prohibited by policy.
Is the management of your network (or parts thereof) outsourced?
No.
Do you have a process for installing operating system and application updates and security patches on servers?
Yes, we are very diligent about applying security updates to operating systems and applications.
Do you also have an emergency process for installing patches outside of the regular patching schedule when high-risk vulnerabilities are identified?
Yes, we carefully consider the risk associated with each new vulnerability and decide whether the patch should be deployed outside of the regular schedule.
How do you determine whether your systems are affected by vulnerabilities that require patching?
We use automated security scans to find software that requires patching + We use the patching mechanisms that are built into the operating systems (e.g., Windows Update).
Do you test security patches before you deploy them to your production systems?
Yes, for important servers we have systems that we test patches on before deploying them to production.
Are your systems configured to log security-relevant events, such as authentication, data access, etc.?
Yes, we have comprehensive logging, including security events, for all relevant services.
Server/Infrastructure
...
UNIX (Including Linux, Solaris etc.).
Do your administrators have personal user accounts and use sudo when elevated privileges are necessary?
Yes, our administrators use sudo (or a similar tool).
Where is the root password kept? (follow-up question to above)
We keep the root password in a secure location (e.g., in an envelope in a safe). It is retrieved only when absolutely necessary. Processes are in place to ensure accountability, and the password is changed after every useBy providing you access to our all security and privacy practices on this pages and on our Trust Center, we think you have all the information necessary to choose, if yasoon apps are a good fit for your company.
To make it even easier for you, we have collected several Q&As on this page for you to browse.
If you still cannot find what you’re looking for, please contact our support team with the missing question and the purchase you want to make.
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Customer Access Requirements/Questions for Login/Account management
Are all identified security, contractual, and regulatory requirements for customer access contractually addressed and remediated prior to granting customers access to data, assets, and information systems?
Not applicable. We do not provide our own user accounts and do not target specific regulatory industries.
Does the system to purchase support MFA enforcement?
We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
Does the system to purchase support SSO e.g. OKTA ?
If configured in Atlassian or Microsoft. In general not really applicable: We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
Does the system to purchase support setting custom complex password policy ?
In general not really applicable: We do not have an own account management. We're using Microsoft and Atlassian accounts and inherit all security settings from Atlassian/ Microsoft.
Network
Do you operate a VPN that allows remote access to your network?
Yes
How is access to the VPN authenticated?
User name and password + second factor (e.g. token).
Is it possible for devices that are not owned and managed by your company to connect to your internal network remotely through VPN?
No, this is prohibited by policy.
Is the management of your network (or parts thereof) outsourced?
No.
Do you have a process for installing operating system and application updates and security patches on servers?
Yes, we are very diligent about applying security updates to operating systems and applications.
Do you also have an emergency process for installing patches outside of the regular patching schedule when high-risk vulnerabilities are identified?
Yes, we carefully consider the risk associated with each new vulnerability and decide whether the patch should be deployed outside of the regular schedule.
How do you determine whether your systems are affected by vulnerabilities that require patching?
We use automated security scans to find software that requires patching + We use the patching mechanisms that are built into the operating systems (e.g., Windows Update).
Do you test security patches before you deploy them to your production systems?
Yes, for important servers we have systems that we test patches on before deploying them to production.
Are your systems configured to log security-relevant events, such as authentication, data access, etc.?
Yes, we have comprehensive logging, including security events, for all relevant services.
Server/Infrastructure
Operating system that are currently in use on your Server:
UNIX (Including Linux, Solaris etc.).
Do your administrators have personal user accounts and use sudo when elevated privileges are necessary?
Yes, our administrators use sudo (or a similar tool).
Where is the root password kept? (follow-up question to above)
We keep the root password in a secure location (e.g., in an envelope in a safe). It is retrieved only when absolutely necessary. Processes are in place to ensure accountability, and the password is changed after every use.
Does the Third Party (or sub-processor) ensure the IT Facilities (Data Centre) that holds customer data, is protected against attacks, accidental damage, natural hazards and unauthorised physical access?
Yes. All customer facing infrastructure is hosted on AWS. Data is stored in Germany. However, our products and services may be provided using resources and servers located in various countries around the world, including the U.S. and other countries. Your information may be transferred and processed by third-parties outside the country where you use our services, including to countries outside the European Economic Area (EEA), where the level of data protection may not be deemed adequate by the European Commission (i.e., where you have fewer rights in relation to your information). We expect that our third-party service providers will comply with the terms of the European Union’s General Data Protection Regulation (GDPR), and that any international data transfers be made under a recognized basis such as the US-EU Privacy Shield, EU Standard Contractual Clauses, and/or Binding Corporate Rules.
Does the Third Party employ Intrusion Detection System (IDS)/Intrusion Prevention System (IPS), Firewalls and other network security services to protect customer services? Please list all services with vendors.
We have signature- and/or anomaly-based IDS/IPS in place, and sensors are in place at strategic points throughout the network. We have firewalls for filtering all inbound and outbound traffic.
Does the Third Party use documented secure build configs for Operating System (OS) and Databases (DBs) supporting customer data?
Restrictions on Software Installation Rules governing the installation of software by users shall be established and implemented in accordance with the Yasoon GmbH Information Security Policy.
Backups
Do you sync data to a different site in near real time?
...
Do you have the capability to recover data for a specific customer in the case of a failure or data loss?
We do have backups of our data and our backend services are spread across different regions, with a DNS loadbalancer in place.
Do you have a retention procedure?
We shall retain data as long as the company has a need for its use, or to meet regulatory or contractual requirements. Once data is no longer needed, it shall be securely disposed of or archived. Data owners, in consultation with legal counsel, may determine retention periods for their data.
...
Users are local administrators on their machines. Since we are a small IT company with only IT trained employees. We confirm that admin access is regularly reviewed.
...
No, all Operating System versions are supported.
Data Management (DPA - Data Processing Addendum (yasoon.com)
Are data input and output integrity routines (i.e., reconciliation and edit checks) implemented for application interfaces and databases to prevent manual or systematic processing errors or corruption of data?
...
All customer data that are stored in our environment are encrypted on data drive level.
Additionally there are data we consider sensitive (e.g. access tokens) not even our support staff should have access to. These data are additionally encrypted within the database with AES-256.
Which data are stored?
We only store content that has been explicitly created by our apps. The exact data varies by used features.
...
Yes. We run a Bug-Bounty-Programm on bugcrowd to encourage security researches looking for vulnerabilities and claim their bug bounties. We run pen-tests multiple times per year.
Are you willing to share a management summary of the most recent penetration testing reports?
...
Staffed reception desk
Guards (shared by entire building)
Motion detectors, Alarms
Electronic access control (e.g., swipe cards)
...
Do you have an auditable process in place for granting and revoking physical access to office facilities? Are physical entry logs kept for at least six months?
Yes and yes.
Do you have a clear desk policy that also requires unattended equipment to be appropriately locked down e.g. Screen Lock, securing laptops with a cable etc.?
...
Do you have written job descriptions for employees with access to confidential or sensitive information?
Yes
Do you have processes in place to ensure that access to data is granted solely on a "need-to-know" basis, in accordance with the job descriptions and responsibilities of users? Do these processes also revoke access when the need no longer exists?
...
Yes, Roles are defined on Azure Entra Id and tied to the job role. Exceptions are handled by tickets and monitored at least once a year.
...
An external policy or notice to the public, users, or customers, describing how you protect the security and privacy of data
Written internal policies, guidelines, and documented practices for the safe handling and protection of data
Internal audits of the security and privacy program
Third-party audits of the security and privacy program
A risk assessment and risk management process to regularly review the threats your company is exposed to
A program to ensure security in your human resources processes
A process to ensure that your service providers and subcontractors are capable of taking appropriate steps to protect sensitive data and systems
Processes and procedures to ensure that security incidents are discovered in a timely manner and dealt with effectively
A change management process to ensure that all changes to networks, systems, and processes are appropriately reviewed
Audits
How often are internal information security and privacy audits performed?
Quarterly or more often.
Does the scope of your internal internal assessment include the entire security and privacy program, as well as all operations, services, and systems that involve access to the customer data or systems that are used in this project?
Yes.
How often does an independent third party perform audits of your security and privacy program? (Note: this should not include penetration tests or other technical assessments; rather, it refers to security reviews of your organizational processes, procedures, and policies.)
...