3 ms·
There are lots of very good (security) reasons this information tends to be kept under wraps. The best thing to do is to involve the security and networks team
by eitally 15y ago
There are lots of very good (security) reasons this information tends to be kept under wraps. The best thing to do is to involve the security and networks teams in your project at the planning phase so you can identify collab points before they become problems. Yes, I have faced this many, many times and it is incredibly frustrating, especially in controlled environments.
- pasbesoin 15y agoIt also helps to earn their trust. It has to be earned, though, and this takes time and ongoing collaboration. Even then, a good team won't break the rules for you. They may, however, be more willing to explain them and to consider rational adaptations. Generally speaking (more for non-startup environments, I guess), getting along well with your Operations folk can be as much of an aid to your work as anything else. Good ones aren't much interested in bullshit (or bullshitting), though, in my experience; the normal workload already provides sufficient quantities of that.