Skip to content
TheChatArchiveThe Chat Archive
gpt-4o-mini-2024-07-18· OpenAIAi2 WildChat-4.8M (AI2)

Can you please consolidate the following paragraphs and correct any spelling and…

  1. User

    Can you please consolidate the following paragraphs and correct any spelling and grammatical errors: What do I need to know?

    A critical aspect of a DevSecOps methodology is to apply best practices to secure your development environment. Bank software and services should be protected from malicious and accidental exposure or modification. The need for security has never been greater given the external threats and expectations from our business, regulators and customers to have secure IT systems and to handle data with care and identifying accountability through code ownership. We currently face a risk of highly protected information, such as passwords, private keys, and tokens, being stored in plain text within our source code management tool. This practice breaches bank policy standards and exposes both the business and our customers to significant risk.

    It’s vital we adhere to bank standards (refer below) to avoid a security breach and disciplinary action from management

    Group IS Classification and Handling Standard

    What do I need to do?

    Navigate to Secrets Remediation & Code Ownership Journey (links to support pages embedded). 

    Engineers to start/continue Remediating Secrets and move out of quarantine organisations GitHub Secrets in Source (Secret Scanning) Dashboard for leadership to address secrets in code is coming soon!  Stay tuned…

    For further support, reach out to the Guardians team via  GitHub Discussions

  2. Assistant

    What You Need to Know

    A key aspect of the DevSecOps methodology is to implement best practices for securing your development environment. It is essential to protect banking software and services from both malicious and accidental exposure or modification. The demand for security has never been greater due to the external threats we face and the expectations from our business, regulators, and customers to maintain secure IT systems and handle data responsibly while ensuring accountability through code ownership.

    Currently, we are at risk of highly sensitive information, such as passwords, private keys, and tokens, being stored in plain text within our source code management tool. This practice violates bank policy standards and poses significant risks to both the business and our customers.

    To mitigate these risks, we must adhere to bank standards (detailed below) to prevent security breaches and avoid disciplinary action from management.

    Group IS Classification and Handling Standard

    What You Need to Do

    1. Navigate to the Secrets Remediation & Code Ownership Journey (links to support pages embedded).
    2. Engineers should start or continue remediating secrets and move them out of quarantine status.
    3. A GitHub Secrets in Source (Secret Scanning) Dashboard for leadership to address secrets in code will be launched soon—stay tuned!

    For further support, please contact the Guardians team via GitHub Discussions.

  3. User

    Can you please consolidate the following paragraphs and correct any spelling and grammatical errors:

    What do I need to know?

    From 26 June 2024, the new on-premises firewall change requests are to be raised in WASP. WASP is now live and ready to be utilised. 

    By using the WASP portal, users will get the following benefits; Get immediate feedback on CBA security policy requirements for your firewall changes. In the past you would have always needed to wait for someone to manually do a full review of your request before you were informed if your change was compliant or not.  However, now using WASP there is inbuilt automation that will identify gaps and alert you straight away of any compliance gaps and uplift required. This will allow our teams to deliver faster while staying secure. Consolidated security and implementation. WASP combines both the security review and implementation into a single request. Provide your firewall change details only once to WASP, then view and track the request details in the portal. ​Take advantage of future improvements. WASP is being continuously improved with your support and feedback. Get familiar with WASP now and be ready to reap the future benefits as they arrive. If you need help raising a request for the first time in WASP or are a reviewer of a request, refer to the below two guides to assist you WASP User Guide/SOP: A detailed guide on how to use the new WASP portal. · Firewall Security Governance Guide: A reference guide for meeting cyber security compliance for your changes. What do I need to do? Visit the WASP Sharepoint site for details on how to access the portal.

    Check out the Firewall Security Governance guide for more details on ensuring your flows are security compliant.

    If you are responsible for a service, make sure your IP ranges are deemed correctly. You can do this by following the process outlined in the Deeming Process and Exceptions SOP.

    Spread the word on this change to help us out!

  4. Assistant

    What You Need to Know

    Starting June 26, 2024, all new on-premises firewall change requests must be submitted through the WASP portal, which is now live and ready for use.

    The WASP portal offers several benefits:

    • Immediate Feedback: Users receive instant feedback on CBA security policy requirements for their firewall changes. Previously, you would have to wait for a manual review to determine compliance with your request. Now, WASP features built-in automation that identifies compliance gaps and alerts you right away, enabling our teams to work faster while maintaining security.

    • Consolidated Security and Implementation: WASP merges the security review and implementation processes into a single request. You only need to provide your firewall change details once and can then view and track the request status in the portal.

    • Future Improvements: WASP will continuously improve based on your feedback and support. Familiarize yourself with WASP now to benefit from enhancements as they become available.

    If you need assistance raising a request for the first time in WASP or if you are a reviewer, please refer to the following guides:

    • WASP User Guide/SOP: A detailed guide on how to navigate the WASP portal.
    • Firewall Security Governance Guide: A reference for ensuring your changes meet cybersecurity compliance.

    What You Need to Do

    1. Visit the WASP SharePoint site for access details to the portal.
    2. Consult the Firewall Security Governance Guide for information on maintaining security compliance.
    3. If you oversee a service, ensure your IP ranges are correctly deemed by following the process outlined in the Deeming Process and Exceptions SOP.

    Please share this update to help spread the word about this change!

  5. User

    Can you please consolidate the following paragraphs and correct any spelling and grammatical errors:: There are now 34 patterns available in the Engineering handbook as of August 2024, with plans for the current library to continue growing. The automated RISE template using AI is due to be in production by the end of September to provide increased efficiency for our teams.  Integrating our library of pre-defined security patterns into DevSecOps framework will enable automated, modular, and scalable security capabilities across different technologies. This will provide CBA staff with the tools they need to deliver faster and safer security assessments.

    Making it easier for squads to improve their velocity by accessing pre-defined patterns to support with security and controls onboarding across a combination of commonly used solutions and control onboarding patterns allowing for repeatable blueprints to be adopted by squads which will assist with velocity across teams

    Self service will be key to implementing and expanding security patterns available - cutting down verification, assessment and pre-approvals for squads on predefined activities

    By providing our Champions and Engineers with modular blueprints for commonly used solutions and control onboarding patterns – this will allow squads to move with velocity and require less engagement with security engineering team, speeding up go live times.

    What do I need to do?

    Ensure you refer to the Security Patterns located within the handbook here and familarise yourself with the new patterns.

  6. Assistant

    What You Need to Know

    As of August 2024, there are now 34 patterns available in the Engineering Handbook, with plans for continued expansion of the library. An automated RISE template utilizing AI is set to go into production by the end of September, enhancing efficiency for our teams.

    Integrating our library of predefined security patterns into the DevSecOps framework will enable automated, modular, and scalable security capabilities across various technologies. This integration will equip CBA staff with the tools necessary to conduct faster and safer security assessments.

    By providing squads with access to predefined patterns, we aim to improve their velocity during security and controls onboarding across commonly used solutions. This will facilitate the adoption of repeatable blueprints, assisting teams in enhancing their efficiency.

    Self-service will be crucial for implementing and expanding the available security patterns, as it will reduce the need for verification, assessment, and pre-approval processes for squads on predefined activities.

    Equipping our Champions and Engineers with modular blueprints for commonly used solutions and control onboarding patterns will allow squads to operate more swiftly and require less engagement with the security engineering team, thereby accelerating go-live times.

    What You Need to Do

    Ensure you refer to the Security Patterns located within the handbook [here](insert link) and familiarize yourself with the new patterns.