Difference between revisions of "FAQ's"

From Charitylog Manual
Jump to: navigation, search
(→‎Security)
(→‎Cybersecurity)
 
(110 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[File:helpheader_small.png|right]]
+
==System requirements==
 +
'''What hardware is required?'''
  
−
==Business==
+
No special hardware is required as Charitylog / Crossdata is an internet (web) application. It is therefore possible to login from any desktop PC, laptop, or mobile device that has an internet connection and browser. It will also run on iPads, most tablets, and smartphones.
  
−
'''When did Dizions start in business?'''
+
'''How fast should my internet connection be?'''
  
−
Dizions started trading in 2004 and was incorporated in 2008.  
+
Connection speeds are rarely an issue these days. A minimum of 2Mbps is recommended. For reference, Ofcom stated that the average UK home broadband speed in September 2022 was 65.3Mbps.
  
−
'''How many people do you employ?'''
+
'''What browser do I need?'''
  
−
Dizions currently employs 25 people
+
Edge, Firefox, Chrome, and Safari are supported. Internet Explorer is no longer supported. It is important that your browser is kept up to date as we only support the two latest versions.
  
−
'''Does your company hold a recognised quality management certification?'''
+
'''What other software do we need?'''
  
−
Yes – ISO 9001:2015 which is annually audited
+
No other software is required, although Microsoft Excel is a useful reporting tool.
  
−
'''What type of business is Charitylog / Crossdata?'''
+
==Licensing & training==
 +
'''How is the system licenced?'''
  
−
We are a software house and Charitylog / Crossdata are brands (trading) names of Dizions Ltd
+
Licensed for 5 concurrent users on the Starter plan, 10 on the One plan, and unlimited on the Plus and Ultimate plans. Additional licenses are available at extra cost.
−
Dizions Ltd is a private limited company registered in Scotland – registration no SC340502
 
−
Registered office: c/o Henderson Kildavaig, 109/14 Swanston Road, Edinburgh EH10 7DS
 
  
−
'''What insurance cover do you have?'''
+
'''What training is provided?'''
  
−
Employers Liability: £10,000,000 (single)
+
A specific number of days will be included in our proposal for Charitylog Standard to ensure the implementation goes smoothly and the setup is matched to your needs and reporting requirements. Charitylog One includes a specific number of getting started sessions.
 +
Additional days may be purchased, as and when needed, for refresher training or for new staff joining the organisation. These days can be delivered remotely. They may also be delivered onsite if the company deems it safe to do so.
  
−
Public Liability: £10,000,000 (single)
+
==User management & security==
 +
'''Does each user have their own unique identifier?'''
  
−
Product Liability: £10,000.000 (single)
+
Yes. There are two levels of login – first, the user needs the organisation username and password. After this, they need their own username and password. Accounts will lock out after 3 invalid login attempts. Resets are then done via an approved administrator with the appropriate validation checks, i.e., confirming that the user is who they say they are.
  
−
Professional Indemnity: £2,000,000 (single)
+
'''What if passwords are forgotten?'''
  
−
Cyber Security: £2,000,000 (single)
+
The local administrator controls this and will provide new passwords subject to rigorous authentication procedures.
  
−
'''Have any claims been made against you in the last five years?'''
+
'''Are strong passwords enforced?'''
  
−
No
+
Yes. The following options regarding passwords apply:
  
−
==Software==
+
Minimum Length of User Username
  
−
'''What hardware is required?'''
+
Minimum number of uppercase characters in Username
  
−
No special hardware is required as Charitylog /Crossdata is an internet (web) application. It is therefore possible to login from any desktop PC, laptop or mobile device that has an internet connection and browser. It will also run on iPads, most tablets and smart phones
+
Minimum number of numeric characters in Username
  
−
'''What other software do we need?'''
+
Number of weeks before user password change required
  
−
No other software is required although MS Excel 2010 (and above) is a useful reporting tool.
+
Minimum length of user passwords
  
−
'''What internet browser(s) are supported?'''
+
Minimum number of uppercase characters in passwords
  
−
We support the latest 2 versions of Edge, Chrome, Firefox and Safari.
+
Minimum number of numeric characters in passwords
  
−
'''How is the system accessed?'''
+
Prevent immediate re-use of the same password if a password is changed.
  
−
From any location with a broadband internet connection. 2Mps minimum recommended.  
+
All passwords are combined with a ‘salt’ before they are encrypted. The salt is periodically changed. This prevents rainbow-based attacks against dictionary passwords. We also check the password entered against previous and current salts to check for reuse.
  
−
'''Does each user have their own unique identifier?'''
+
'''Does the system use hard-coded or clear text passwords in the code, database, or other files?'''
  
−
Yes. There are two levels of login – first the user needs the organisation username and password, after this they need their own user name and password. Accounts will lock out after 3 invalid login attempts.  Resets are then done via an approved administrator with the appropriate validation checks i.e. confirming that the user is who they say they are.  
+
No hard-coded passwords exist in the software.
  
−
'''What if passwords are forgotten?'''
+
'''Does the system allow different user profiles that permit different access / read / write / delete / create actions for individuals and groups of users to be established?'''
  
−
The local administrator controls this and will provide new passwords subject to rigorous authentication procedures.  
+
Yes.
  
−
'''Does the system ensure passwords are not hard coded and no clear text passwords exist in the code, database or other files?'''
+
'''Does the system time out after a period of inactivity and log the user out?'''
  
−
Yes. No hard coded passwords exist in the software. We prevent passwords from being saved in browsers.  
+
Yes, after 60 minutes. This can be reduced at an organisation level.
  
−
'''Does the system allow different user profiles that permit different access / read / write / delete / create actions for individuals and groups of users to be established?'''
+
'''What technical and organisational measures do we use to restrict and regulate our employee’s access to customer’s data?'''
  
−
Yes
+
Only named employees have access to client data, specifically for Data Migration services. This access is restricted by permissions on the network. Access to the production servers is also restricted to a controlled location. Access to data is audited including any failed access. If a client requests a change to their data, this is done using an administration panel to complete the update without displaying it. It is also carried out in a test environment first.
  
−
'''Does the system time out after a period of inactivity and log the user out?'''
+
'''Do we operate a password change policy?'''
  
−
Yes. Currently a ‘default’ 60 minutes is applied but this may be changed at an organisation level to allow you to set your own inactivity period
+
Yes, our systems require strong passwords, minimum of 8 characters, including capitals, numbers, and special characters. Passwords require changing every 90 days. Users cannot use the previous 10 passwords.
  
−
'''Access to certain system files, program files and data is restricted to administrator role?'''
+
'''Can individual user activity be monitored and audited?'''
  
−
Yes. This is controlled by the access rights given to a group of users – they can be kept out of all administration and security options as required. There is a system wide process which allows pages to be made visible, access allowed, editing allowed and, where relevant, new record entry allowed.  
+
The system maintains a secure audit trail that records all successful and unsuccessful attempts to access the system including user, date, and time. The IP address from which the login was attempted is also recorded.
  
−
'''Can data be restricted to named individuals or groups and hidden from others?'''
+
==Software features & integrations==
 +
'''What other apps does the system integrate with?'''
  
−
Yes. The local administrator is able to manage the ‘visibility’ of individual and /or group data sets as required
+
Your website, to streamline inbound referrals, recruitment etc., using our embedded web forms.
 +
Loqate for address lookups using postcodes
 +
TextAnywhere for sending SMS messages
 +
Microsoft for email and calendars
 +
Google maps, for displaying the geographical distribution of your volunteers, service users, etc., and time/distance calculations.
  
 
'''Can I share information securely with project partners?'''
 
'''Can I share information securely with project partners?'''
  
−
Yes. The local administrator can control this through the ‘branch’ facility.  
+
Yes. The local administrator can control this through the branch feature.
  
−
'''How is the system upgraded?'''
+
'''Can data be restricted to named individuals or groups and hidden from others?'''
  
−
Software upgrades are scheduled to take place at around 4 monthly intervals. Details of forthcoming upgrades are posted on the website.  
+
Yes. The local administrator is able to manage the visibility of individual and/or group data sets as required.
  
−
'''Can we integrate Charitylog / Crossdata into our website?'''
+
'''Can we integrate the system into our website?'''
  
−
Yes  
+
Yes, our web forms can be used to collect self-referrals, or from others such as GPs, straight from your website. You'll need to edit the code on your website, but it's a single line change, and our support team will show you how to do it.
  
−
'''What documentation will be made available to support the application?'''
+
==Support & documentation==
 +
'''What documentation is available?'''
  
−
All features are thoroughly documented in our manual, which is what you are reading now.
+
All features are thoroughly documented in our manual, which is what you are reading now! Every page in the application has a page in the manual - click the question mark in the top right.
 +
We record videos on specific topics and embed them into the manual together with uploading them to our webinar library for viewing whenever required.
  
−
'''What help is available?'''
+
'''Do you have a support desk?'''
  
−
The online manual is ‘context sensitive’ and will link automatically to the correct page in the manual containing the information.
+
A telephone support line is also available during office hours (9 am – 5 pm) from Monday to Friday. We also provide support via email.
  
−
A telephone support line is also available during office hours (9am – 5pm) from Monday to Friday. We also provide support via email. 
+
==Software updates & bug fixes==
 +
'''How is the system upgraded?'''
  
−
We record videos on specific topics and embed them into the manual together with uploading them to our webinar library for viewing whenever required.  
+
Software upgrades are scheduled to take place at around 4-month intervals. Details of forthcoming upgrades are posted on the website, and you can subscribe to update emails on your user record.
  
 
'''How are bugs fixed?'''
 
'''How are bugs fixed?'''
  
−
All bugs are reported through a formalised reporting procedure which firstly establishes that the report is in fact a bug and then, if confirmed, allocates resources to its resolution.  
+
All bugs are reported through a formalised reporting procedure which firstly establishes that the report is in fact a bug and then, if confirmed, allocates resources to its resolution.
 +
Bugs which prevent the operation of the system are given a high priority and are usually fixed in a few hours, whilst others with lower impact may take longer. In very low priority cases, the resolution may be delayed until the next software release stage.
  
−
Bugs which prevent operation of the system are given a high priority and are usually fixed in a few hours whilst others with lower impact may take longer. In very low priority cases the resolution may be delayed until the next software release stage.
+
'''What software development methodology is used?'''
  
−
'''Can individual user activity be monitored and audited?'''
+
Dizions uses a tried and tested approach which incorporates elements of Agile, such as a focus on user stories over rigid specifications, short iterations, and face-to-face interactions. We do not believe rigidly sticking to any particular methodology is compatible with the continuous improvement needed for ISO9001. All code changes are logged as RFCs in our ticketing system, with a defined workflow which includes code review by another developer, static code analysis, and testing by our QA team.
 +
 
 +
==Infrastructure & data management==
 +
'''Where is data stored?'''
 +
 
 +
The system is hosted on AWS. AWS is divided into regions, and each region is divided into Availability Zones. We only use the UK region, which ensures your data stays in the UK. The live databases can only be in a single zone, but the backups are spread across multiple zones within the UK region, to provide resiliency against, for instance, the physical destruction of a data centre.
 +
There is no need for any local data storage, e.g., on your laptop, although clients may take local backups of their data when required. In this situation, the client will be responsible for the security of the local backups.
  
−
The system maintains a secure audit trail that records all successful and unsuccessful attempts to access the system including user, date and time.  The IP address from which the login was attempted is also recorded.
+
'''Will any of my data be shared or mined?'''
  
−
==Infrastructure & Data Centre==
+
No. Your data is your own. Your T&Cs with Dizions, and Dizions' T&Cs with AWS, specifically rule this out.
  
−
'''Where is data stored?'''
+
'''Are the database servers shared by other systems?'''
  
−
The system is hosted on dedicated servers in the UK by Rackspace (www.rackspace.co.uk) and Amazon Web Services (AWS). Each organisation has its own database(s) within the datacentre. It uses a MySQL database with PHP as the main programming language. There is no need for any local data storage, although clients may take local backups of their data when required. In this situation the client will be responsible for the security of the local backups.
+
No. Read about AWS's industry-leading logical separation here. Each organisation has its own database.
  
 
'''Is the data encrypted at rest?'''
 
'''Is the data encrypted at rest?'''
Line 127: Line 144:
 
Yes, using AES with 256-bit encryption (high).
 
Yes, using AES with 256-bit encryption (high).
  
−
'''Datacentre security'''
+
'''Do we use a shared SAN for backups?'''
−
 
 
−
The data centres are unbranded and unmarked. Physical access to devices within a data centre is restricted to authorised personnel which prevents access to unauthorised areas. (e.g. the Inventory Controller does not have access to the servers and devices within the data halls).
 
  
−
A card reader and biometric access is required to enter the facility (finger printing), and further card reader access required to enter data centre floor. Security cameras recorded by digital video recorder. Bomb proof film installed behind all windowed areas. Fully fenced perimeter.
+
No, we do not use Storage Area Networks. Read more about AWS's industry-leading logical separation [https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDurability.html here].
  
−
'''Is the database server shared by other systems?'''
+
'''What security measures are in place at the data centre?'''
  
−
No
+
Read about AWS' robust defences on [https://aws.amazon.com/compliance/data-center/controls/ this page].
  
−
'''Is any data stored outside the EU?'''
+
'''What is the uptime, and how do we maximize it?'''
  
−
No
+
The system is designed to be resilient, with many components duplicated so that in the event of failure, another component can take over.
 +
The system has three layers: application, database, and backup. Each layer has its own resilience. The application layer, e.g., web servers, is spread across multiple availability zones and can scale up or down depending on load. As a result of this, typical uptime is much higher than the SLA figure of 99.9%, e.g. in 2023 the figure was 99.95%.
  
−
'''Do you use a shared SAN for backups?'''
+
'''How do we deploy updates to servers and infrastructure?'''
  
−
No
+
System updates are scheduled monthly with a separate change management process. Servers are deployed using infrastructure-as-code, which allows us to spin up new environments or roll back changes rapidly.
−
 
 
−
'''Do you deploy updates to servers and infrastructure?'''
 
−
 
 
−
All security updates are tested and deployed as soon as possible. General updates and version changes are tested and deployed in line with our planned new releases of the software.
 
  
 
'''What process and procedures are applied to remove unnecessary services from running automatically on operating systems?'''
 
'''What process and procedures are applied to remove unnecessary services from running automatically on operating systems?'''
  
−
Our servers only run the services and software for hosting our software and data.  Our systems are not connected to the production servers; run only approved services and software and are audited monthly.
+
We use a ‘hardened’ operating system build based on industry standards such as CIS (Centre for Internet Security). This includes removing unnecessary services and using a minimal build for deployment.
−
 
 
−
'''Are all pre-installed system account passwords changed from their defaults on your internal systems?'''
 
−
 
 
−
Our production servers and internal systems will have all manufacturer passwords replaced in line with our Information Management System policies. This is also a requirement for our ISO 27001 and Cyber Essentials Plus certification.
 
−
 
 
−
'''Do you use Antivirus Software and Personal Firewalls?'''
 
−
 
 
−
Hardware and/or Software is deployed at all of our network gateways including our Production and Email Servers.  In additional to the gateways we also protect each device individually.  The solutions that we use are industry standard provided by Avast, Cisco and Microsoft (Email Servers).
 
−
 
 
−
'''How do you physically transfer data?'''
 
−
 
 
−
As a cloud-based software developer we only transfer data electronically using SSL/TLS using 256-bit encryption.
 
−
 
 
−
'''Do you have a wireless network?'''
 
−
 
 
−
We have wireless access which is restricted by MAC address and password for office equipment only.  Guest access is isolated via a VLAN, preventing access to the internal network.
 
  
−
==GDPR==
+
==Data protection & compliance==
 +
'''Is the system GDPR compliant?'''
  
−
'''Is Charitylog / Crossdata GDPR compliant?'''
+
Dizions as a business is. There is no formal accreditation for software products to be GDPR compliant. The system does however, have an integrated set of tools to enable your organisation to be fully compliant with the GDPR.
−
 
 
−
There is no formal accreditation for software products to be GDPR ‘compliant’. Charitylog / Crossdata does however, have an integrated set of tools to enable your organisation to be fully compliant with the GDPR (General Data Protection Regulation).
 
  
 
'''Is Dizions Ltd registered with the Information Commissioners Office?'''
 
'''Is Dizions Ltd registered with the Information Commissioners Office?'''
  
−
Yes – we comply with the General Data Protection Regulation (GDPR) and are registered with the ICO - number ZA029219.  
+
Yes. Our registration number is Z2460686.
  
−
'''Have you appointed a Data Protection Officer (DPO)?'''
+
'''Have we appointed a Data Protection Officer (DPO)?'''
  
−
Yes, they may be contacted at our normal office address or by email dpo@dizions.co.uk
+
Yes, we have a DPO who oversees our compliance with the GDPR and our Data Protection policies.
  
 
'''Freedom of Information Act (FOIA)'''
 
'''Freedom of Information Act (FOIA)'''
  
−
Whilst Charitylog / Crossdata does not directly come under the scope of this Act it would co-operate in any FOIA request should this become necessary.
+
The Freedom of Information Act (FOIA) applies to public authorities such as local authorities and government agencies. Dizions Ltd is not a public authority, therefore FOIA does not apply to us. However, we are registered with the Information Commissioner’s Office as a data processor and are compliant with GDPR. Our services are used by some public authorities, who will likely require their use of our systems to comply with FOIA. We will cooperate with these requirements where appropriate.
−
 
 
−
The Act covers any recorded information that is held by a public authority in England, Wales and Northern Ireland, and by UK-wide public authorities based in Scotland. 
 
−
 
 
−
Public authorities include government departments, local authorities, the NHS, state schools and police forces. However, the Act does not necessarily cover every organisation that receives public money. For example, it does not cover some charities that receive grants and certain private sector organisations that perform public functions.  
 
−
 
 
−
Whilst Charitylog / Crossdata does not directly come under the scope of this Act it would co-operate in any FOIA request should this become necessary.
 
−
 
 
−
==Security==
 
−
 
 
−
'''What SSL security is used?'''
 
−
 
 
−
Thawte V3. TLS 1.2, AES with 256-bit encryption (High); RSA with 2048 bit exchange.
 
−
 
 
−
'''What security certification do you have?'''
 
−
 
 
−
We hold ISO27001:2013 and Cyber Essential Plus accreditations which are annually audited.
 
  
−
'''Are your staff trained for information security?'''
+
'''How do we handle data breaches?'''
  
−
All staff undergo internal training specifically for data protection and information security.
+
We take data security very seriously. In the unlikely event of a data breach, we have a formal Incident Response Procedure in place. This involves identifying the breach, containing it, and notifying affected clients and the ICO within 72 hours. We also perform a root cause analysis to prevent a recurrence.
  
−
'''HMG Security Policy Framework 2018'''
+
'''Do you confirm to HMG Security Policy Framework 2018?'''
  
−
The new simplified government security classification scheme uses just three levels:
+
The HMG Security Policy Framework is a set of mandatory security policies for government departments. While it doesn’t apply directly to us, we do take it into account when designing our systems to ensure that they meet or exceed government security standards.
  
−
1 OFFICIAL: This category is for the majority of information created or processed by government and includes both routine business and some sensitive information, which could have damaging consequences if lost, stolen or published in the media, but are not subject to a heightened threat profile.
+
==Cybersecurity==
 +
'''What SSL security is used for data encryption in transit?'''
  
−
2 SECRET: Very sensitive information that justifies heightened protective measures to defend against determined and highly capable threats. For example, where compromise could seriously damage military capabilities, international relations or the investigation of serious organised crime.  
+
The system uses SSL (Secure Sockets Layer) certificates to establish an encrypted connection between the user’s browser and the server. This prevents third parties from eavesdropping on the communication. We use 256-bit, TLS 1.3 SSL certificates, the same level of encryption used by banks and financial institutions.
  
−
3 TOP SECRET: This category of information is the most sensitive requiring the highest levels of protection from the most serious threats. For example, where compromise could cause widespread loss of life or else threaten the security or economic wellbeing of the country or friendly nations.
+
'''What security certification do we have?'''
  
−
These new classifications are intended to liberate and modernise Government IT by simplifying the approach to secure data transfer and introducing greater commonality to support update of share services.  
+
We have Cyber Essentials Plus and ISO27001 certification.
  
−
The most used grade of sensitive information – OFFICIAL – is the level which Charitylog/Crossdata systems and policies adopt.
+
'''Are our staff trained for information security?'''
  
−
'''Is the data encrypted at rest?'''
+
Yes, all staff undergo regular information security training. This includes GDPR training, awareness of phishing attacks, and secure coding practices for our developers.
−
 
 
−
Yes, using AES with 256-bit encryption (high)
 
  
 
'''What quality checking is performed on code to prevent vulnerability such as SQL injection?'''
 
'''What quality checking is performed on code to prevent vulnerability such as SQL injection?'''
  
−
All user input, whether through POST or GET, is validated against its defined properties in a data dictionary and screened for what may be regarded as invalid characters as appropriate. We use standard escaping processes. Our method of implementing MySQL does not allow multiple queries to be submitted in a single query string. We only present single queries and a multiple query would create an error which would be reported back to us automatically, showing the query submitted.
+
All code is peer-reviewed by another developer, and static code analysis is used to identify potential security vulnerabilities. SQL injection vulnerabilities are specifically checked for, and any user input is sanitized before being passed to the database.
−
 
 
−
We have XSS (cross-site-scripting) checks implemented on every page. A failure would stop the application and report the incident to us.
 
−
 
 
−
'''What type of firewalls are used?'''
 
−
 
 
−
Cisco ASA 5505 Sec+
 
−
 
 
−
'''Are strong passwords enforced?'''
 
−
 
 
−
Yes. The following options regarding passwords apply: -
 
−
 
 
−
Minimum Length of User Username; 
 
−
 
 
−
Minimum number of upper case characters in Username; 
 
−
 
 
−
Minimum number of numeric characters in Username; 
 
−
 
 
−
Number of weeks before user password change required; 
 
−
 
 
−
Minimum length of user passwords; 
 
−
 
 
−
Minimum number of upper case characters in password; 
 
−
 
 
−
Minimum number of numeric characters in password; 
 
−
 
 
−
Prevent immediate re-use of the same password if a password is changed.
 
−
 
 
−
All passwords are combined with a ‘salt’ before they are encrypted. The salt is periodically changed. This prevents rainbow based attacks against dictionary passwords. We also check the password entered against previous and current salts to check for reuse.  
 
  
 
'''How is data protected during transfer to and from the server?'''
 
'''How is data protected during transfer to and from the server?'''
  
−
As a cloud-based software developer we only transfer data electronically using SSL/TLS using 256-bit encryption. The system stores and transmits all passwords in encrypted form.  
+
Data is transferred using SSL, which ensures that the data is encrypted during transmission. Additionally, all data is encrypted at rest using AES-256 encryption.
  
 
'''Is the software penetration tested?'''
 
'''Is the software penetration tested?'''
  
−
Yes, every year we have a in-depth test conducted by a Certified Cyber Security Consultancy. This check covers both the software and the hardware for a range of potential vulnerabilities. The tests involve a mixture of automated tools, such as SSL scans, and manual tests by an expert tester.  
+
Yes, we commission external penetration tests at least once per year, using a CREST-certified supplier.
  
 
'''Can I have a copy of the latest penetration report?'''
 
'''Can I have a copy of the latest penetration report?'''
  
−
No, this is a commercially sensitive document of a technical nature, which is not shared with 3rd parties. However, we can provide a ‘letter of opinion’ from the certifying agency if required. In line with our ISO 27001 accreditation, we act on any recommendations from the report in a timely manner.  
+
No, this is a commercially sensitive document of a technical nature, which is not shared with 3rd parties. In line with our ISO 27001 accreditation, we act on any recommendations from the report in a timely manner.
  
 
'''Can I conduct my own penetration test?'''
 
'''Can I conduct my own penetration test?'''
  
−
No. We commission pen test annually, which is conducted by a CREST accredited organisation. If we let other companies conduct such work independently, we would have to audit them as part of our ISO27001 accreditation, to make sure they were keeping their qualifications and accreditations up to date. We are also contractually obliged by the data centre to provide them with details of the scope all tests, and give them sufficient notice to avoid false alerts by their own mitigation systems.  
+
No. We commission a pen test annually, which is conducted by a CREST accredited organisation. If we let other companies conduct such work independently, we would have to audit them as part of our ISO27001 accreditation, to make sure they were keeping their qualifications and accreditations up to date. We are also contractually obliged by the data centre to provide them with details of the scope all tests, and give them sufficient notice to avoid false alerts by their own mitigation systems.
  
−
'''Do you commission penetration tests on your internal office network and systems?'''
+
'''Do we commission penetration tests on our internal office network and systems?'''
  
−
A penetration test is performed annually by an independent body as part of our Cyber Essentials Plus accreditation. The independent body qualifications include CLAS, CCP and IASME & CE+ A and is IASME Gold
+
Yes, our internal office network and systems are also subject to penetration tests to ensure they are secure.
  
−
'''Should I connect to Charitylog / Crossdata using public WIFI?'''
+
'''How do I reduce the risk of cyber attacks?'''
  
−
There are 2 types of public WIFI: unsecured and secured. You can tell if a network is secured because it will prompt you for a password when you connect.
+
You can reduce the risk of cyber attacks by ensuring your systems and software are up to date, using strong passwords, and being vigilant against phishing attacks. We also recommend using antivirus software and enabling two-factor authentication.
−
Most security experts recommend against using unsecured WIFI for any purpose whatsoever, often these can be people trying to obtain your data.  
 
−
For additional security when using a secured public network, you may want to consider using a VPN.
 
−
Using a VPN means you are connected securely to your office, and the connection to our servers will go through the IP address of your office, which has the added benefit that you can then use the Restricted IP Addresses feature to block access from unknown locations.
 
  
−
'''What are the business continuity arrangements?'''
+
'''What is the policy for the use of laptops and mobile devices?'''
  
−
Backups are made automatically every 24hrs in the datacentre and stored offsite for 28 days. The restore process is tested monthly. There is a security controlled option to take a data backup locally, which will provide all the SQL needed to rebuild the database elsewhere.
+
Laptops and mobile devices must be password-protected and have encryption enabled. They should also be kept up to date with the latest security patches. We recommend enabling remote wipe functionality in case a device is lost or stolen.
  
−
If the whole datacentre and the backup location was destroyed (i.e. the servers and the backups were destroyed at the same time), the database could only be rebuilt from a local backup. Clients can make their own local backups (under secure conditions) should they wish. 
+
'''What is our policy for the use of removable media such as memory sticks and CD/DVDs?'''
  
−
There is also an ESCROW agreement provided by a solicitor who would release source code and software tools to enable the system to be rebuilt elsewhere, if it was proven that the system was no longer supported.  
+
We do not use any removable media. All removable media is physically blocked on our network.
  
−
'''How do you handle data breaches?'''
+
'''Should I connect to the system using public WIFI?'''
  
−
In the unlikely event of a data breach being encountered on the Dizions servers, we would contact your registered administrators immediately. We would also advise the Information Commissioner’s Office (ICO) if necessary.
+
We advise against connecting to the system using public WIFI, as these networks are often not secure. If you must use public WIFI, use a VPN to encrypt your connection.
  
−
'''Do you operate a password change policy?'''
+
'''What are the business continuity arrangements?'''
  
−
Yes, our systems require strong passwords, minimum of 8 characters, including capitals, numbers and special characters. Passwords require changing every 90 days. Users cannot use the previous 10 passwords.  
+
We have a robust Business Continuity Plan (BCP) that is tested regularly. This includes regular backups, a disaster recovery plan, and the ability to work remotely if necessary.
  
−
'''What is the policy for the use of laptops and mobile devices?'''
+
==Company information & legal==
 +
'''What type of business is Dizions?'''
  
−
We have users with Laptops and Phones which are protected by encryptions and two factor authentication.  We only use our cloud services to store our client information. None of the devices has direct access to our production servers. Devices are centrally managed.  
+
We are a software house and Charitylog / Crossdata are brands (trading) names of Dizions Ltd. Dizions Ltd is a private limited company registered in Scotland – registration no SC340502. Registered office: c/o Henderson Kildavaig, 109/14 Swanston Road, Edinburgh EH10 7DS.
  
−
'''What is your policy for the use of removable media such as memory sticks and CD/DVDs?'''
+
'''When did Dizions start in business?'''
  
−
We do not use any removable media. All removable media is physically blocked on our network.
+
Dizions started trading in 2004 and was incorporated in 2008.
  
−
'''What technical and organisational measures do you use to restrict and regulate your employee’s access to customer’s data?'''
+
'''How many people do we employ?'''
  
−
Only named employees have access to client data, specifically for Data Migration services.  This access is restricted by permissions on the network.  Access to the production servers is also restricted to a controlled location.  Access to data is audited including any failed access.  If a client requests a change to their data this is done using an administration panel to complete the update without displaying it. It is also carried out in a test environment first.
+
Dizions currently employs 27 people.
  
−
==Other==
+
'''Does our company hold a recognised quality management certification?'''
  
−
'''How is Charitylog / Crossdata licenced?'''
+
Yes, Dizions Ltd is ISO 9001:2015 certified.
  
−
Charitylog / Crossdata is licenced for up to 50 concurrent users, as standard. Additional licences are available at extra cost.
+
'''What insurance cover do we have?'''
  
−
'''What training is provided?'''
+
Dizions Ltd has public liability insurance, employers' liability insurance, and professional indemnity insurance. Details can be provided upon request.
  
−
A specific number of days will be included in our proposal for Charitylog Standard to ensure the implementation goes smoothly and the setup is matched to your needs and reporting requirements. Charitylog One includes a specific number of getting started sessions.
+
'''Have any claims been made against us in the last five years?'''
  
−
Additional days may be purchased, as and when needed, for refresher training or for new staff joining the organisation. These days can be delivered remotely. They may also be delivered onsite if the company deems it safe to do so.  
+
No claims have been made against Dizions Ltd in the last five years.
  
−
'''How do you remove my data at the end of the contract if I don't renew?'''
+
==Termination & data removal==
 +
'''How do I extract my data at the end of the contract if I don't renew?'''
  
−
There are 2 areas to consider - the database(s) and the backup files.  
+
At the end of the contract, you will have the option to download your data as a SQL file and/or spreadsheets.
  
−
Simply deleting a database can leave fragmented data on the disk. To prevent this, the data within the database is first overwritten multiple times, which means that even with physical access to the disk, an attacker would not be able to recover the deleted data.
+
'''What happens to my data?'''
  
−
The backup files are created using a Managed Backup, which is an automated process. Your data will remain for the duration of the back retention period. 
+
Once you have extracted your data, your databases and documents will be securely deleted from our systems. After that, they will be retained as part of our automated backups for 28 days. This is all managed through AWS retention policies, so you can be assured that your data is permanently deleted and irrecoverable after that point.
−
For additional peace of mind, for physical servers, we arrange for the storage media to be physically destroyed when it's decommissioned and a certificate of destruction provided.  
 
  
−
'''What is a VPN?'''
+
'''Is the storage media physically destroyed to ensure my data is really deleted?'''
  
−
A Virtual Private Network (VPN) is a connection between a device and a host (usually an office).  A VPN can be used to create a secure and encrypted connection between devices.  It is recommended that this is setup and configured by an IT professional.  Please contact your IT support for further information.
+
This used to be common practice when decommissioning dedicated physical servers, and often involved shredding or crushing hard drives! Fortunately with cloud computing, securely erasing data is baked into the platform. See [https://aws.amazon.com/compliance/data-privacy/ AWS Data Privacy]

Latest revision as of 16:54, 5 December 2024

System requirements

What hardware is required?

No special hardware is required as Charitylog / Crossdata is an internet (web) application. It is therefore possible to login from any desktop PC, laptop, or mobile device that has an internet connection and browser. It will also run on iPads, most tablets, and smartphones.

How fast should my internet connection be?

Connection speeds are rarely an issue these days. A minimum of 2Mbps is recommended. For reference, Ofcom stated that the average UK home broadband speed in September 2022 was 65.3Mbps.

What browser do I need?

Edge, Firefox, Chrome, and Safari are supported. Internet Explorer is no longer supported. It is important that your browser is kept up to date as we only support the two latest versions.

What other software do we need?

No other software is required, although Microsoft Excel is a useful reporting tool.

Licensing & training

How is the system licenced?

Licensed for 5 concurrent users on the Starter plan, 10 on the One plan, and unlimited on the Plus and Ultimate plans. Additional licenses are available at extra cost.

What training is provided?

A specific number of days will be included in our proposal for Charitylog Standard to ensure the implementation goes smoothly and the setup is matched to your needs and reporting requirements. Charitylog One includes a specific number of getting started sessions. Additional days may be purchased, as and when needed, for refresher training or for new staff joining the organisation. These days can be delivered remotely. They may also be delivered onsite if the company deems it safe to do so.

User management & security

Does each user have their own unique identifier?

Yes. There are two levels of login – first, the user needs the organisation username and password. After this, they need their own username and password. Accounts will lock out after 3 invalid login attempts. Resets are then done via an approved administrator with the appropriate validation checks, i.e., confirming that the user is who they say they are.

What if passwords are forgotten?

The local administrator controls this and will provide new passwords subject to rigorous authentication procedures.

Are strong passwords enforced?

Yes. The following options regarding passwords apply:

Minimum Length of User Username

Minimum number of uppercase characters in Username

Minimum number of numeric characters in Username

Number of weeks before user password change required

Minimum length of user passwords

Minimum number of uppercase characters in passwords

Minimum number of numeric characters in passwords

Prevent immediate re-use of the same password if a password is changed.

All passwords are combined with a ‘salt’ before they are encrypted. The salt is periodically changed. This prevents rainbow-based attacks against dictionary passwords. We also check the password entered against previous and current salts to check for reuse.

Does the system use hard-coded or clear text passwords in the code, database, or other files?

No hard-coded passwords exist in the software.

Does the system allow different user profiles that permit different access / read / write / delete / create actions for individuals and groups of users to be established?

Yes.

Does the system time out after a period of inactivity and log the user out?

Yes, after 60 minutes. This can be reduced at an organisation level.

What technical and organisational measures do we use to restrict and regulate our employee’s access to customer’s data?

Only named employees have access to client data, specifically for Data Migration services. This access is restricted by permissions on the network. Access to the production servers is also restricted to a controlled location. Access to data is audited including any failed access. If a client requests a change to their data, this is done using an administration panel to complete the update without displaying it. It is also carried out in a test environment first.

Do we operate a password change policy?

Yes, our systems require strong passwords, minimum of 8 characters, including capitals, numbers, and special characters. Passwords require changing every 90 days. Users cannot use the previous 10 passwords.

Can individual user activity be monitored and audited?

The system maintains a secure audit trail that records all successful and unsuccessful attempts to access the system including user, date, and time. The IP address from which the login was attempted is also recorded.

Software features & integrations

What other apps does the system integrate with?

Your website, to streamline inbound referrals, recruitment etc., using our embedded web forms. Loqate for address lookups using postcodes TextAnywhere for sending SMS messages Microsoft for email and calendars Google maps, for displaying the geographical distribution of your volunteers, service users, etc., and time/distance calculations.

Can I share information securely with project partners?

Yes. The local administrator can control this through the branch feature.

Can data be restricted to named individuals or groups and hidden from others?

Yes. The local administrator is able to manage the visibility of individual and/or group data sets as required.

Can we integrate the system into our website?

Yes, our web forms can be used to collect self-referrals, or from others such as GPs, straight from your website. You'll need to edit the code on your website, but it's a single line change, and our support team will show you how to do it.

Support & documentation

What documentation is available?

All features are thoroughly documented in our manual, which is what you are reading now! Every page in the application has a page in the manual - click the question mark in the top right. We record videos on specific topics and embed them into the manual together with uploading them to our webinar library for viewing whenever required.

Do you have a support desk?

A telephone support line is also available during office hours (9 am – 5 pm) from Monday to Friday. We also provide support via email.

Software updates & bug fixes

How is the system upgraded?

Software upgrades are scheduled to take place at around 4-month intervals. Details of forthcoming upgrades are posted on the website, and you can subscribe to update emails on your user record.

How are bugs fixed?

All bugs are reported through a formalised reporting procedure which firstly establishes that the report is in fact a bug and then, if confirmed, allocates resources to its resolution. Bugs which prevent the operation of the system are given a high priority and are usually fixed in a few hours, whilst others with lower impact may take longer. In very low priority cases, the resolution may be delayed until the next software release stage.

What software development methodology is used?

Dizions uses a tried and tested approach which incorporates elements of Agile, such as a focus on user stories over rigid specifications, short iterations, and face-to-face interactions. We do not believe rigidly sticking to any particular methodology is compatible with the continuous improvement needed for ISO9001. All code changes are logged as RFCs in our ticketing system, with a defined workflow which includes code review by another developer, static code analysis, and testing by our QA team.

Infrastructure & data management

Where is data stored?

The system is hosted on AWS. AWS is divided into regions, and each region is divided into Availability Zones. We only use the UK region, which ensures your data stays in the UK. The live databases can only be in a single zone, but the backups are spread across multiple zones within the UK region, to provide resiliency against, for instance, the physical destruction of a data centre. There is no need for any local data storage, e.g., on your laptop, although clients may take local backups of their data when required. In this situation, the client will be responsible for the security of the local backups.

Will any of my data be shared or mined?

No. Your data is your own. Your T&Cs with Dizions, and Dizions' T&Cs with AWS, specifically rule this out.

Are the database servers shared by other systems?

No. Read about AWS's industry-leading logical separation here. Each organisation has its own database.

Is the data encrypted at rest?

Yes, using AES with 256-bit encryption (high).

Do we use a shared SAN for backups?

No, we do not use Storage Area Networks. Read more about AWS's industry-leading logical separation here.

What security measures are in place at the data centre?

Read about AWS' robust defences on this page.

What is the uptime, and how do we maximize it?

The system is designed to be resilient, with many components duplicated so that in the event of failure, another component can take over. The system has three layers: application, database, and backup. Each layer has its own resilience. The application layer, e.g., web servers, is spread across multiple availability zones and can scale up or down depending on load. As a result of this, typical uptime is much higher than the SLA figure of 99.9%, e.g. in 2023 the figure was 99.95%.

How do we deploy updates to servers and infrastructure?

System updates are scheduled monthly with a separate change management process. Servers are deployed using infrastructure-as-code, which allows us to spin up new environments or roll back changes rapidly.

What process and procedures are applied to remove unnecessary services from running automatically on operating systems?

We use a ‘hardened’ operating system build based on industry standards such as CIS (Centre for Internet Security). This includes removing unnecessary services and using a minimal build for deployment.

Data protection & compliance

Is the system GDPR compliant?

Dizions as a business is. There is no formal accreditation for software products to be GDPR compliant. The system does however, have an integrated set of tools to enable your organisation to be fully compliant with the GDPR.

Is Dizions Ltd registered with the Information Commissioners Office?

Yes. Our registration number is Z2460686.

Have we appointed a Data Protection Officer (DPO)?

Yes, we have a DPO who oversees our compliance with the GDPR and our Data Protection policies.

Freedom of Information Act (FOIA)

The Freedom of Information Act (FOIA) applies to public authorities such as local authorities and government agencies. Dizions Ltd is not a public authority, therefore FOIA does not apply to us. However, we are registered with the Information Commissioner’s Office as a data processor and are compliant with GDPR. Our services are used by some public authorities, who will likely require their use of our systems to comply with FOIA. We will cooperate with these requirements where appropriate.

How do we handle data breaches?

We take data security very seriously. In the unlikely event of a data breach, we have a formal Incident Response Procedure in place. This involves identifying the breach, containing it, and notifying affected clients and the ICO within 72 hours. We also perform a root cause analysis to prevent a recurrence.

Do you confirm to HMG Security Policy Framework 2018?

The HMG Security Policy Framework is a set of mandatory security policies for government departments. While it doesn’t apply directly to us, we do take it into account when designing our systems to ensure that they meet or exceed government security standards.

Cybersecurity

What SSL security is used for data encryption in transit?

The system uses SSL (Secure Sockets Layer) certificates to establish an encrypted connection between the user’s browser and the server. This prevents third parties from eavesdropping on the communication. We use 256-bit, TLS 1.3 SSL certificates, the same level of encryption used by banks and financial institutions.

What security certification do we have?

We have Cyber Essentials Plus and ISO27001 certification.

Are our staff trained for information security?

Yes, all staff undergo regular information security training. This includes GDPR training, awareness of phishing attacks, and secure coding practices for our developers.

What quality checking is performed on code to prevent vulnerability such as SQL injection?

All code is peer-reviewed by another developer, and static code analysis is used to identify potential security vulnerabilities. SQL injection vulnerabilities are specifically checked for, and any user input is sanitized before being passed to the database.

How is data protected during transfer to and from the server?

Data is transferred using SSL, which ensures that the data is encrypted during transmission. Additionally, all data is encrypted at rest using AES-256 encryption.

Is the software penetration tested?

Yes, we commission external penetration tests at least once per year, using a CREST-certified supplier.

Can I have a copy of the latest penetration report?

No, this is a commercially sensitive document of a technical nature, which is not shared with 3rd parties. In line with our ISO 27001 accreditation, we act on any recommendations from the report in a timely manner.

Can I conduct my own penetration test?

No. We commission a pen test annually, which is conducted by a CREST accredited organisation. If we let other companies conduct such work independently, we would have to audit them as part of our ISO27001 accreditation, to make sure they were keeping their qualifications and accreditations up to date. We are also contractually obliged by the data centre to provide them with details of the scope all tests, and give them sufficient notice to avoid false alerts by their own mitigation systems.

Do we commission penetration tests on our internal office network and systems?

Yes, our internal office network and systems are also subject to penetration tests to ensure they are secure.

How do I reduce the risk of cyber attacks?

You can reduce the risk of cyber attacks by ensuring your systems and software are up to date, using strong passwords, and being vigilant against phishing attacks. We also recommend using antivirus software and enabling two-factor authentication.

What is the policy for the use of laptops and mobile devices?

Laptops and mobile devices must be password-protected and have encryption enabled. They should also be kept up to date with the latest security patches. We recommend enabling remote wipe functionality in case a device is lost or stolen.

What is our policy for the use of removable media such as memory sticks and CD/DVDs?

We do not use any removable media. All removable media is physically blocked on our network.

Should I connect to the system using public WIFI?

We advise against connecting to the system using public WIFI, as these networks are often not secure. If you must use public WIFI, use a VPN to encrypt your connection.

What are the business continuity arrangements?

We have a robust Business Continuity Plan (BCP) that is tested regularly. This includes regular backups, a disaster recovery plan, and the ability to work remotely if necessary.

Company information & legal

What type of business is Dizions?

We are a software house and Charitylog / Crossdata are brands (trading) names of Dizions Ltd. Dizions Ltd is a private limited company registered in Scotland – registration no SC340502. Registered office: c/o Henderson Kildavaig, 109/14 Swanston Road, Edinburgh EH10 7DS.

When did Dizions start in business?

Dizions started trading in 2004 and was incorporated in 2008.

How many people do we employ?

Dizions currently employs 27 people.

Does our company hold a recognised quality management certification?

Yes, Dizions Ltd is ISO 9001:2015 certified.

What insurance cover do we have?

Dizions Ltd has public liability insurance, employers' liability insurance, and professional indemnity insurance. Details can be provided upon request.

Have any claims been made against us in the last five years?

No claims have been made against Dizions Ltd in the last five years.

Termination & data removal

How do I extract my data at the end of the contract if I don't renew?

At the end of the contract, you will have the option to download your data as a SQL file and/or spreadsheets.

What happens to my data?

Once you have extracted your data, your databases and documents will be securely deleted from our systems. After that, they will be retained as part of our automated backups for 28 days. This is all managed through AWS retention policies, so you can be assured that your data is permanently deleted and irrecoverable after that point.

Is the storage media physically destroyed to ensure my data is really deleted?

This used to be common practice when decommissioning dedicated physical servers, and often involved shredding or crushing hard drives! Fortunately with cloud computing, securely erasing data is baked into the platform. See AWS Data Privacy

Retrieved from ‘https://wiki.dizions.co.uk/index.php?title=FAQ%27s&oldid=20199’