• Public

REST API Group

Skip Feed

  1. Shuning, Veracode Community Manager (Veracode)

    April 7, 2021 at 2:12 PM

    ⚠️ Announcement: this group will be archived at the end of the week.

     

    We wanted to give you a heads-up that we’re archiving this user group at the end of this week, to help centralize discussions in the Integrations topical forum where you can continue to ask questions, exchange ideas, learn and share best practices, and get updates from the Veracode team.

     

    🔔To share feedback and stay on top of new discussions about REST APIs, follow #Integrations API​ ​ and enable email notifications.

    Expand Post
    • 414 views

  2. Tim J (Veracode PM) (Veracode) asked a question.

    October 6, 2020 at 1:44 PM
    👉New guidance available: Generating Swagger client code for multiple Veracode APIs

    Hi all, just wanted to let you know that a new knowledge base article on how to create Swagger client code when using multiple Veracode APIs together. A few customers have had questions about this and we wanted to clarify the approach needed. (tl;dr: put each API in its own package using a configuration file when generating client code.)

     

    Here's the article: https://community.veracode.com/s/article/Generate-swagger-clients

     

    Please let me know if you have any questions!

    Expand Post
    • 287 views

  3. 1 of 2

    • JSwindle018785 (Community Member)

      Thanks. I believe it is valuable to have documentation for the overlap between API Security Top 10 and OWASP Top 10. That would allow us to produce documentation of what from API Security Top 10 is covered by Veracode scans. We'd then produce internal documentation of coverage for what's not covered.

  5. Shuning, Veracode Community Manager (Veracode) to ugor245446 (Community Member):

    August 13, 2019 at 6:44 PM

    Hello!

     

    Welcome to the Veracode Community! My name is Shuning and I am your Community Manager who will be your guide and resource as you navigate in the space. I'd love to learn more about your goals with Veracode so that I can better connect resources for you in the Community and help achieve your goals.

     

    On a separated note, in case you haven't heard about it already, I wanted to make sure you're aware of the Integrations Hub that's meant to be a one-stop shop where you can find all Integrations resources and documentations.

     

    If you have any question going forward, you can always DM me. Happy to help any time!

     

    -Shuning

     

    Expand Post
    • 2 comments
    • 515 views
    1 of 2

    • Shuning, Veracode Community Manager (Veracode)

      Hi @ugor245446 (Community Member)​ ! I have posted a question for you in the @REST API Group (Archived)​ 🙂 See if folks there have some insights to share.

       

      Btw, I have noticed that you're not registered as a customer in the community (with the personal email you registered with), leading to limited visibility to content, features made available only for customers. If you're a Veracode customer, as soon as you can provide your work email, I can help update your profile very quickly! 🙂

      Expand Post

  6. WSharif383182 (Community Member) asked a question.

    June 17, 2019 at 3:44 PM
    To Understand On DueDate In API

    I hope this the right place to ask. I am referring to this api https://help.veracode.com/viewer/book-attachment/LMv_dtSHyb7iIxAQznC~9w/FZkc8EDX1EikoWknGahc_Q.

    On

    "FindingRuleViolation": {

    "type": "object",

    "properties": {

    "dueDate": {

    "type": "string",

    "format": "date-time",

    "description": "The date that the fix is due by, taking into account the grace period. The date/time is formatted as per RFC3339 and ISO-8601. The timezone is UTC."

    },

     

    I am aware there is "fix by date" column in report from Veracode static scan. Is it this refer to the same data?

     

    How this "fix by date" being tracked? Is it from the day one the application being scan?

     

    In a scenario, where the application being re-scan in next 30 days, do this "dueDate" will be change as well even the same flaw is appeared?

     

    Hope to hear from you soon.

    Expand Post
    • 1 answer
    • 469 views

    • Tim J (Veracode PM) (Veracode)

      Hi @WSharif383182 (Community Member)​ , thanks for the question. The "dueDate" field in Findings API should be the same as the "fix by date" in the Veracode reports.

       

      These dates are set based on the policy assigned to the application, and will appear if the policy includes a "grace period" for findings -- e.g. if the grace period for a High severity finding is 30 days, the due date will be 30 days from the date on which the finding was first found.

       

      The dueDate should not change when a rescan; as long as flaw matching from scan to scan is successful, we will always calculate it based on the original scan date. It might change if the policy is changed, but should not change otherwise.

       

      Hope this is helpful!

      Expand Post

  7. Tim J (Veracode PM) (Veracode)

    June 13, 2019 at 11:42 AM

    Hi all, We have posted an update to the Findings Swagger file that includes the following improvements:

     

    1. New endpoint underneath findings: findings/statistics

    This endpoint provides summary level information for the set of findings you request. You can hit the endpoint with most if not all the query options that /findings supports and get a summary for that set of findings. The output looks like this:

     

    {

     "resolution": {

     "MITIGATED": 1,

     "CANNOT_REPRODUCE": 0,

     "MITIGATED_BY_CUSTOM_CLEANSER": 0, ...

     },

     "resolution_status": {

      "AUTOMATED": 1423,

      "NONE": 4274,

      "APPROVED": 1,

      "PROPOSED": 0,

      "REJECTED": 0

     },

     "severity": {

      "0": 0,

      "1": 0,

      "2": 1617,

      "3": 3388,

      "4": 468,

      "5": 225

     },

     "status": {

      "CLOSED": 1424,

      "OPEN": 4274

     },

     "cwe": {

      "209": 1467,

      "80": 1397,

      "113": 777, ....

     },

     "_links": {

    ...

    }}

     

    2. Bug fixes

    • Corrected the issue that MOBILE was showing up as an option for querying for scan_type
    • Removed the /scans endpoint since it hasn't been implemented
    • Updated the swagger for various things connected with MPT

     

    The updated Swagger has been linked from the Help Center. Enjoy!

    Expand Post
    • 515 views

  8. siwilson (Community Member) asked a question.

    May 16, 2019 at 12:42 PM
    Has there been an sort of documentation yet, or does anyone have any information on the exact calls that can be used for the Findings API?

    I'm looking for something fairly extensive, not just a few basic calls.   I realize this API is still in the EA phase, but I was just wondering if anyone had used it enough to know a lot more of what can be done with it.

    • 12 answers
    • 922 views
    1 of 12

    • siwilson (Community Member)

      ​Wow, I didn't notice any of that before, but that's exactly what I was looking for.  Didn't noticed it was being paged out.   That's the issue then.

      Thanks again Tim.

End of Feed
8 Chatter Feed Items

Group Details