Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Penetration Testing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Penetration Testing

    One of my apps/customers is nearing a penetration test. I've never been through this before. Negotiations are underway about the details. What caused me to pause and post here was this: The testing company wants a login and a waiver against damages of any kind.

    This is mostly understandable - the user most likely to cause damage is one with login creds - whether he/she should have them or not. And it seems fairly standard to waive any damage claims.

    In these days of internet searches I feel fairly informed on the subject, but wonder if anyone's been through this and most particularly if you (a) gave them keys to the door and (b) agreed not to hold them liable for any damage?

    I'm comfortable our app is in good shape for this, but still want to do what I can to protect our interests

    Thanks for any comments
    -Steve
    sigpic

    #2
    Re: Penetration Testing

    I don't know. To me it sounds like this is the point where you need to speak to an attorney.
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Penetration Testing

      I'd say common sense should be the rule here.
      Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

      Comment


        #4
        Re: Penetration Testing

        Damages? It is an app and data, back both up and get the test. If something goes wrong it would be better to find out in a controlled situation rather than a legitimate hack.

        I had one done before, not with Alpha as the source code but something else. They found a minor error and I worked with the Vendor to plug the vulnerability.

        Comment


          #5
          Re: Penetration Testing

          Overall I'm with Jeremy on this. But, this is a SAAS application with many clients all with data that is treated and viewed to near-HIPAA standards. We're taking steps to insure that the testing company behaves appropriately. This test is being ordered and paid for by a very large new client so we don't have the same control as if we were hiring the testing.
          -Steve
          sigpic

          Comment


            #6
            Re: Penetration Testing

            Can you create a VM and copy the app there? Like a phase 1 test. If that shows anything, then fix that before the full blown test. Your other clients would be happier with this also.
            Pat Bremkamp
            MindKicks Consulting

            Comment


              #7
              Re: Penetration Testing

              Pat - our client is paying a contractor for the test. So, we don't know much about their methods, tools, plan, etc. and wouldn't be able to run a pre-test trial. We may learn a little more as we get closer to the event. I'm hoping and kind of expecting it'll be a "non-event".
              -Steve
              sigpic

              Comment


                #8
                Re: Penetration Testing

                I've been through a few of these and although they get you to sign the agreements, I have found that they know what they are doing. Being experts, they definitely know enough to not carry out any damaging or very intrusive actions.
                For instance, if they see a weak point in the system that is open to a brute force attack, they usually just tell you about it. They don't need to prove it to you and are confident enough with what they found to be able to explain it rather than actually carrying out the attack.
                It is a penetration test after all; not a stress test.

                I have never given them any type of account login information though. And especially not some sort of super-user account info. They would usually create an account like any other user and see what they can do with it. They would work with me though and call me, for example, when they were about to confirm an eCommerce order that I would then make sure doesn't get fulfilled. If they couldn't get me on the phone, they would postpone that part of the test.

                Most of the time, I could find no indication that they were even trying to penetrate the system.

                EDIT: Come to think of it... they also had us get our infrastructure hosting service to sign an agreement so that they would not be surprised by suspicious activity and over-react by shutting systems down. I actually would not work with security experts if they did not have you sign some agreements.
                Last edited by jgrannis; February 04, 2019, 04:35 PM.

                Comment

                Working...
                X