Skip to main content

A book to start the journey

About me:
I love books, specially history books, biographies and autobiographies.  I love learning from other people's experiences, struggles, shortcomings and success.

Career History:
I have been a pre-sales systems engineer (SE) since September of 2010 after working in various industry's IT departments as a network/security engineer. (My LinkedIn profile)


I was introduced rather late to "Great Demo!" by Peter E. Cohen.  James Cabe who is one of the smartest people I know recommended this book at my on boarding at Fortinet. I think it is essential to learn the principles of pre-sales engineering and what a "real demonstration" is before even getting in front of customers.
Now, the book talk about software demonstrations but I think it applies to any technical pre-sales engagement and demonstration.

My good friend and colleague Eric Hastings came up with an idea of standardizing and streamlining our demonstrations, proof of concepts and pilots (yes they are quite different) here at Fortinet. There will me more to come on that.


And finally,  The picture in the following article explains the role masterfully.




Comments

Soheil Samouhi said…
two more books I came across that might be helpful as well:

https://www.amazon.com/dp/1596933399?ref_=pfb_4g4274e2kc12j3ginc7gnhf0hf13&tag=hydfbook0e-20&ascsubtag=pfb-P01-V01-O3-T1-HI-4DCJUB


https://www.amazon.com/dp/1596933399?ref_=pfb_4g4274e2kc12j3ginc7gnhf0hf13&tag=hydfbook0e-20&ascsubtag=pfb-P01-V01-O3-T1-HI-4DCJUB

Popular posts from this blog

MPLS vs VPN (Internet Connection) and power

This topic has been covered extensively by experts. What has not been covered in my opinion, is the underlying and fundamental change of transport infrastructure and specially power. The traditional WAN transport mechanisms are solid in terms of power normalization all through the last mile.  With the new (or not so new) shift towards commercially available Internet connections (namely DSL and Cable), customers need to watch out for excessive power coming through those lines and the respective modems and into their edge devices. There are surge protectors out there with "ethernet in/out" ports which could be used to mitigate this problem. Happy conversation out there...

There is sizing, and then there is right sizing

When it comes to firewall upgrades or refreshes, you need to know your: Current traffic volumes and mixture Session counts Number of users Current and future Internet or private connection pipes Current and future throughput requirements (VPN, SSL Inspection and decryption, etc...) Current and future unified threat management (UTM) needs Interface requirements  Number of IP devices LAG requirements  Future growth  I am sure you can come up with more variables and compare it to the vendors specification sheet in order to come up with an accurate size or model of a security appliance.  However, nothing beats a real/live test with a traffic generator.   When I usually size a box based on the customer's requirements, I also factor in real life examples, previous firewall implementations and what the Internet/application traffic trends. I have heard so many "oh we are not going to use such and such application" or "we will never use SSL inspection"...

“If you want to make beautiful music, you must play the black and the white notes together.” ― Richard M. Nixon

Does your product integrate with other security products? At this point, you should hate product silos (point products) as much as I do.   I understand and respect “divide and conquer” or “best of breed” strategies. I also understand having different security vendors at different layers of the network could possibly prevent an incident better (one vendor might not see/catch a vulnerability but another might have a signature or way of catching it). But isn’t it time to ask your vendors how and if they can work with each other? So what we (vendors) are competitors?   If by integrating with each other, we are able to increase the return on investment (ROI) for the customer, then why not (I know it might sound naive and unaware, but could you just imagine ). Vendors have application programming interfaces (APIs) for interaction with other platforms.   However, customers have to have application development resources to write code for these APIs, and that's not answ...