Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Feb 15, 2017

Application Security Groups (ASGs) on Bluemix Local

We would like to leverage ASGs on Bluemix Local. By design (CloudFoundry), ASG defines allow rules. This means that you can only add new rules to the existing ones.
On Bluemix Local, the default rules allow all traffic (all destinations, all protocols). As a consequence, there is no way to actually control which destinations are accessible from the apps. Adding new allow rules to the default allow all rule is useless.

The proposed solution to make it possible to leverage ASGs on Bluemix Local is to change the default rules to allow the traffic to the minimum (only what is required for Bluemix Local to run).

  • Guest
    Feb 26, 2017

    Catherine - would you please tag the customers who have asked for this today?

  • Guest
    Feb 16, 2017

    More clarifications on the use case. Several Lines of Business have their apps hosted on the Bluemix Local Platform. An organization is assigned to each LoB. Each LoB can decide to have several spaces, one for test, one for integration, one for pre-production, etc. Apps need to reach backends (CICS, DBs, MQs on mainframe for example) hosted on corporate private network (outside of Bluemix, but still in private network).  We want to make sure that Bluemix apps from LoB1 can access backends from LoB1 and only from LoB1,  apps from LoB2 can access backends from LoB2 and only from LoB2, etc. We can even imagine than for a given LoB, the access to the pre-production backends is allowed only for the apps in the pre-production space (and not for the apps in the integration or test spaces).

  • Guest
    Feb 16, 2017

    Catherine - I seem to be missing the "why" here. What's the underlying use-case? Are they trying to restrict Local apps from connecting to other internal local apps and endpoints or external ones? If internal, why so? If external, why not do it with a proxy?