Search results

Information Security Policy Creation

Examples of Information Security Objectives are:
- decrease the impact and/or number of information security incidents by 30% in 12 months
- increase revenue of service XYZ by 5% in 12 months
- win a new customer in 6 months
- increase market share by 3% in 12 months

For further information, see:

• ISO 27001 control objectives – Why are they important? https://advisera.com/27001academy/blog/2012/04/10/iso-27001-control-objectives-why-are-they-important/

Statement for logs retention periods regarding critical assets

ISO 27001 does not prescribe retention periods for logs.

To define proper retention periods, you need to perform a risk assessment and identify applicable legal requirements.

In case your risk assessment and requirements do not provide a proper reference, you can try starting with a retention time of one year.

For further information, see:

• Logging and monitoring according to ISO 27001 A.12.4 https://advisera.com/27001academy/logging-according-to-iso-27001/

Distributor vs Supplier quality agreement

Quality agreement should be with the actual manufacturer because you need to be sure that the device is produced in accordance with ISO 13485 and MDR.  

ISM Policy

ISO 27001 does not prescribe which objectives to define, so you can use objectives related to your business strategy, to specific customers and regulators you must comply with. Additionally, you can also use more specific objectives related to security controls, security processes, etc.

Some specific examples are:

• win a new customer in 6 months
• increase market share by 3% in 12 months

For further information, see:

• ISO 27001 control objectives – Why are they important? https://advisera.com/27001academy/blog/2012/04/10/iso-27001-control-objectives-why-are-they-important/

• Custom Control Creation

  Considering your stated situation (Having operating system software and databases that are at the end-of-support life cycle), suggested assets, vulnerabilities, and threats, with respective controls are:

  • Assets: “Operating systems” and “Database management systems”
  • Vulnerabilities: “Rules for software and its databases not clearly defined” and “Requirements for software development not clearly defined”
  • Threats: “Maintenance errors” and “Application error”
  • Controls: “A.8.25 - Secure development life cycle” and “A.8.8  Management of technical vulnerabilities”

  Please note that end-of-support is part of the retirement step of an asset life cycle management process (in this case, applied to assets operating system software and databases), and so it is an expected situation for IT operations.

  Considering that, the vulnerability, in this case, would be related to not knowing what to do by this time.

• ISO 27001 certification

  a) Is it necessary for me to artificially amend the risk evaluation to achieve the 10% Unacceptable risks?

  First of all, sorry for this confusion.

  This message is intended for companies that are implementing ISO 27001 for the first time. Since you already have implemented controls that reduce risks to an acceptable level, you do not need to include additional risks if you do not need to.

  However, security risks are evolving very quickly, so it is likely that you do have some unacceptable risks that you did not record previously. It is recommended that you try to identify these new risks.

  b) Will the certification auditor not pass the certification audit if there is no risk treatment actions?

  Please note that risk treatment actions are needed only in case you have relevant risks to treat or want to make changes in existing controls (e.g., to update technologies or include improvements).

  Since it is likely that your company is facing some new risks, the certification auditor will want to see if you managed to identify them. If you can convince the auditor that there are certainly no new risks, then you will pass the surveillance audit.

   c) What is your recommendation?

  In your situation, recommendations are:

  • Regarding risk assessment, take this opportunity to review your risk assessment, because after the last assessment new risks may have risen that may require treatment
  • Regarding risk treatment actions, in case you do not have relevant risks to treat, try to look for improvement opportunities in implemented controls and document them as risk treatment actions. This will show the auditor a greater level of maturity of your ISMS.

  For further information, see:

  • Risk treatment https://advisera.com/27001academy/iso-27001-risk-assessment-treatment-management/#treatment

  • ISO 17025 audit

    You said:
    
    I know "what" to look out for, but not "how" to or "who" to."

    For clarity, the “what to look at for” are the audit criteria and in this case any ISO 17025 mandatory as well as additional laboratory defined requirements for calibrations. These are clause 6.4 and 6.5 requirements of ISO 17025.

    To answer how to go about it and who the auditee is, you need to identify what documented information exists within the management system – all polices, plans, processes, and procedures which have been put in place. Using an ISO  17025 audit checklist firstly record whether mandatory documentation is in place. Secondly read through the documentation and determine how the laboratory documents their approach to support a requirement and or policy. Look for objective evidence to see that what is stated as done is in fact being done. In each case documentation should clearly define responsibilities. These are the personnel which should be interviewed during the audit (the auditee) and asked to provide evidence against the audit criteria. For example there is a mandatory need for calibration programme (ISO 17025 6.4.7) . Ask to see the programme, select a few items from the list and call for the calibration certificates as evidence of the programme working. Also look for evidence that the programme is reviewed and adjusted as necessary in order to maintain confidence in the status of calibration. For example, if there was a nonconformance raised or risk identified about lack of calibration or the external calibration interval, the programme should reflect that.  Find out if the laboratory specifies their review period and if so, assess whether that review period is complied with. If they do specify the review period, best practice is at least yearly or before / after management revied as required to keep the program active

    The following will provide more information for you on Auditing and ISO 17025:
    The White paper (free for download) How to perform an internal audit using ISO 19011 at https://info.advisera.com/free-download/how-to-perform-an-internal-audit-using-iso-19011
    The article ISO 17025 technical internal audit: The basics at https://advisera.com/17025academy/blog/2020/11/10/iso-17025-technical-internal-audit-the-basics/
    The ISO 17025 document template: Internal Audit Procedure at https://advisera.com/17025academy/documentation/internal-audit-procedure
    The Five Internal Audit Procedure appendices Internal Audit Program, Internal Audit Checklist, Audit Nonconformity Report, Internal Audit Process Checklist and Internal Audit Report are available separately from the procedure link above; or included in the toolkit for preview and purchase.

  • 27001 query

    From the provided requirement, a risk assessment covering specifically the payment services is enough to fulfill it. Depending upon where this process is performed, you may also consider risks related to supplier management (e.g., the payment process is performed using a cloud service provider).

    For further information, see:

    • ISO 27001 Risk Assessment, Treatment, & Management: The Complete Guide https://advisera.com/27001academy/iso-27001-risk-assessment-treatment-management/