Welcome to my babbling stream of consciousness!

A Statement of Intent

In this technological age we are constantly seeing shifting paradigms and neologisms to go along with them. Every time I get a grasp on things, something else comes along that reveals a completely new path that can be leveraged and encompassed to make new and exciting visions for how things can be done. One has to have a truly voracious appetite to keep up with even a fraction of the changes going on in this new era.

Here in this blog, I hope to brain dump on some of my thoughts on these changes and concepts that are new to me, share neat things I come across, and hopefully garner conversation and technical exchange around such things. While I share my thoughts and opinions, I hope to hear what others have to say, to learn, and expand my horizons. Constructive criticism is not only desired, but required! Hopefully, there will be explanations and connections I have made in here as well that may help others to grasp some complex topics easier.

Statements and concepts in this blog are things being explored by someone who is still (and hopefully always will be) learning. There are those who have a far deeper understanding of these domains than I, as well as corporately vetted and published documents that are less opinionated. I invite people to discuss things they may disagree with, point out any inaccuracies, and let me know if they see things that need refined or updated in conjunction with the aforementioned shifting paradigms.

With that, welcome to my babbling stream of consciousness... or if you are boring, my blog.


Comments

Post a Comment

Popular posts from this blog

Firewall, IDS, IDP, WAF, API Gateway: Choose Your Shield

To long a read? Feel free to jump to the bottom for the exciting conclusion! Often in US Federal we see different requirements and use cases arise than our commercial counterparts. Quite often I might get asked to provide insight into security, identity, and compliance queries in the same way I might ask for insight on team development or CICD requirements from my commercial focused brethren. It just so happens that this week I have provided some insights on three of four discussions around the role of our API Gateway in enterprise security. The role of an API Gateway in enterprise architecture in general always seems to bring up interesting discussion points (can it replace my load balancer?), but none more so than enterprise security. I have often heard of API Gateways jokingly referred to as a 'Swiss army knife' because you can really do so much with them. Often I find myself saying to both customers and colleagues that 'It's not what you can do with it, it is what
Read more

API Security - The Next Generation with Elastic Beam

Image
The Prime Directive - Open more technology doors without increasing risk. I can distinctly recall being fresh in the Federally focused aspect of my career and having a conversation with a customer where he said to me "We don't measure failure in dollars, but in the loss of lives." It was a powerful statement that has stuck with me ever since that speaks to the sensitivity of the data and the critical nature of US Federal systems. The challenge becomes that this creates a situation where disruption can be far from ideal, and risk-adverse strategies with a strong focus on security are often paramount.  And yet, recent times have brought an explosion of new technologies and capabilities with tactical and practical value that cannot be ignored. Servicemen and women look to utilize their own devices to accessing PII focused data and services, or basic applications such as time sheets, without all the hassle of going through CAC-secured desktop systems. Officers in command wa
Read more

REST API Best Practices: HTTP Status Codes and You, Part 2(xx) - Status 200; Success!

Ah, the HTTP Status Code 200 series. Request sent by client, received by server, understood and processed, and a response has been sent. He shoots he scores, GOALLLLLLLL! The status code 200 series is the "Pass GO, Collect 200 Dollars" of HTTP Responses, this is the result for which we strive. In this part of the series, I will cover some of the major HTTP 200 series response codes and how they can be used as part of an effective REST API strategy. Do note, that I will not cover them all here, but I want to touch on some of the ones you may already know, and some you may not know, but might easily start to use in API development process. So with that, let's start at the very beginning, a very good place to start! HTTP Status Code 200 - OK What it means: Success! Everything worked out. What content to expect returned: This largely depends on your request verb. For example, a GET request might return the requested resource, such as a JSON formatted response. A P
Read more