DoD CIO Enterprise DevSecOps Reference Design - Summaryauthentication (mTLS), an encrypted communication tunnel between containers, strong identities per Pod using certificates, and whitelisting rather than blacklisting. Services that support the security0 码力 | 8 页 | 3.38 MB | 6 月前3
HW弹药库之红队作战⼿册账号密码 从各第三⽅历史漏洞库中查找⽬标曾经泄露的 各种敏感账号密码 [ 国内⽬标很好使 ] ⽬标Svn⾥泄露的各类 敏感⽂件 ⽹站⽬录扫描 [ 查找⽬标⽹站泄露的各类敏感⽂件, ⽹站备份⽂件, 敏感配置⽂件, 源码 , 别⼈的webshell, 等等等...] ⽬标站点⾃身在前端代码中泄露的各种敏感信息 fofa / shodan / bing / google hacking 深度利⽤ 弱⼝令, 敏感信息泄露 ] LDAP [ 默认⼯作在tcp 389端⼝, 未授权访问, 弱⼝令, 敏感账号密码泄露 ] SMTP [ 默认⼯作在tcp 25端⼝, 服务错误配置导致的⽤户名枚举漏洞, 弱⼝令, 敏感信息泄露 ] POP3 [ 默认⼯作在tcp 110端⼝, 弱⼝令, 敏感信息泄露 ] IMAP [ 默认⼯作在tcp 143端⼝, 弱⼝令 计划任务 各种错误服务配置利⽤ 0x06 内⽹安全 [敏感信息搜集,防御重点,可在此项严格限制各种系统内置命 令执⾏] 搜集当前已控 "跳板机" 的各类敏感信息 注: 如下某些操作肯定是需要事先⾃⼰想办法先拿到管理权限后才能正常进⾏的,此处不再赘述 查看当前shell权限 及 详细系统内核版本 获取当前系统的 详细ip配置,包括 所在域, ip, 掩码, ⽹关,0 码力 | 19 页 | 1.20 MB | 1 年前3
The Goal - A Process of Ongoing ImprovementQA?Two types of resources ● Bottleneck - any resource whose capacity is equal to or less than the demand placed upon it ● Non-Bottleneck - any resource whose capacity is greater than the demand placed divide that time into four elements: ● Setup - the time the part spends waiting for a resource, while the resource is preparing itself to work on the part ● Process time - the amount of time the part time the part spends in line for a resource while the resource is busy working on something else ahead of it ● Wait time - the time the part waits, not for a resource, but for another part so they can0 码力 | 6 页 | 100.81 KB | 6 月前3
The Phoenix Projectpiling up at the bottleneck.” Resource Utilization “The wait time is the ‘percentage of time busy’ divided by the ‘percentage of time idle.’ In other words, if a resource is fifty percent busy, then if a resource is ninety percent busy, the wait time is ‘ninety percent divided by ten percent’, or nine hours. In other words, our task would wait in queue nine times longer than if the resource were0 码力 | 3 页 | 154.45 KB | 6 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014This approach focuses on an integrated government-contractor release team, but could be more resource intensive. Figure 7 Multiple Release Team Example Management of Agile development requires includes a risk of failure, and continuous prototyping gives program managers and users a powerful resource to reduce risk, quickly integrate new technologies, and identify innovative solutions that leverage using a services-type contract for Agile development. Contract incentives are time consuming and resource intensive to manage, and can lead to a contentious working relationship between the government0 码力 | 74 页 | 3.57 MB | 6 月前3
The DevOps Handbookrun in parallel iii. Generally, limit manual testing if automated tests haven’t passed iv. For resource intensive suites, performance tests, IA, execute as frequently as possible i. WRITE OUR AUTOMATED0 码力 | 8 页 | 23.08 KB | 6 月前3
A Seat at the Table: IT Leadership in the Age of Agility - Part 2project sponsors (1) developing a formal proposal that incorporates estimated benefits, risks, and resource requirements and (2) submitting the proposal to decision makers who select preferred investments0 码力 | 7 页 | 387.61 KB | 6 月前3
共 7 条
- 1













