Giter VIP home page Giter VIP logo

Comments (5)

royb-legit avatar royb-legit commented on July 21, 2024

Thanks @ajh-

  1. Did this happen for only one policy?
  2. Can you paste a few lines above the remediation steps (starting from the policy title)
  3. Can you attach logs?

from legitify.

royb-legit avatar royb-legit commented on July 21, 2024

@ajh- thanks to @sagic-orca your bug was fixed in version 1.0.9.

from legitify.

ajh- avatar ajh- commented on July 21, 2024

@royb-legit @sagic-orca thanks for taking this on. I should've been more specific upfront. This happens for all policies when outputted as markdown. Unfortunately, just tested v1.0.9 and still have the same issue.

I'm assuming applying @sagic-orca's fix to formatter_markdown.go should also remediate my current issue?

from legitify.

royb-legit avatar royb-legit commented on July 21, 2024

@ajh- thanks for resurfacing this.
Version 1.0.10 should fix it, could you please check it?

from legitify.

ajh- avatar ajh- commented on July 21, 2024

@royb-legit Perfect, just tested it and it looks like it is fixed. Thanks!

I will add, with this formatting update, the blockquote section is now displayed as multiple sections instead of being one contiguous section. Not the end of the world, but just wanted to let you know.

For example:

Default Branch Should Require Code Review ⛔

In order to comply with separation of duties principle and enforce secure code practices, a code review should be mandatory using the source-code-management system's built-in enforcement. This option is found in the branch protection setting of the repository.

Policy Name: code_review_not_required
Namespace: repository
Severity: HIGH ⛔

Threat:

  • Users can merge code without being reviewed, which can lead to insecure code reaching the main branch and production.

Remediation Steps:

Note: The remediation steps apply to legacy branch protections, rules set-based protection should be updated from the rules set page

  1. Make sure you have admin permissions
  2. Go to the repo's settings page
  3. Enter 'Branches' tab
  4. Under 'Branch protection rules'
  5. Click 'Edit' on the default branch rule
  6. Check 'Require a pull request before merging'
  7. Check 'Require approvals'
  8. Set 'Required number of approvals before merging' to 1 or more
  9. Click 'Save changes'

Violations:

Link to repository: https://test.com/test
Auxiliary Info:

  • Entity Id: 77
  • Entity Name: test

from legitify.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.